SSVD actually runs a rather small test but it is a MR job in local mode, there's nothing to cut down there in terms of size (not much anyway). It's just what it takes to initialize and run all jobs (and since it is local, it is also single threaded, so it actually runs V and U jobs sequentially instead of parallel so it's even longer because of that (4 jobs stringed all in all).
But i will take a look, although even if i reduce solution size, it will still likely not reduce running time by more than 20%. On Thu, Dec 8, 2011 at 5:42 AM, David Murgatroyd <[email protected]> wrote: > > > > > On Dec 8, 2011, at 8:36 AM, Grant Ingersoll <[email protected]> wrote: > >> MAHOUT-916 and 917 are attempts to address the running time of our tests. >> As Sean rightfully pointed out, there are probably opportunities to simply >> cut down the sizes of some of these tests w/o effecting there correctness. >> To that end, if people can take a look at: >> https://builds.apache.org/job/Mahout-Quality/1237/testReport/junit/ >> >> You can get a sense as to which tests are taking a long time. The main >> culprits are: >> 1. Vectorizer >> 2. SSVD >> 3. K-Means >> 4. taste.hadoop.item >> 5. taste.hadoop.als >> 6. PFPGrowth >> >> >> -Grant >> >> -------------------------------------------- >> Grant Ingersoll >> http://www.lucidimagination.com >> >> >>
