About https://issues.apache.org/jira/browse/MAHOUT-170 Enable Java compile optimize flag during buildAny reason why we shouldnt add the -XX:+AggressiveOpts -XX:+UseFastAccessorMethods flags. to the JVM.
Robin On Tue, Oct 6, 2009 at 2:55 PM, Robin Anil <robin.a...@gmail.com> wrote: > I am currently converting entire Bayes/CBayes to Writable + Writable > Comparable StringTuple format, instead of using Text. So that takes care of > MAHOUT-148 > I would be taking up MAHOUT-157 to finish the parallel version, Once > Bayes/Cbayes looks clean enough. > > > > On Tue, Oct 6, 2009 at 2:41 PM, Isabel Drost <isa...@apache.org> wrote: > >> On Tue, 6 Oct 2009 09:18:38 +0100 >> Sean Owen <sro...@gmail.com> wrote: >> >> > How is everyone feeling about 0.2? it's a week later, some issues have >> > been closed. If there hasn't been movement on an issue marked for 0.2 >> > in the last week, might it be a good time to consider moving it to >> > 0.3? or else I guess I'm interested to hear a game plan on anything >> > that hasn't been touched in a week, yet must be part of 0.2, keeping >> > in mind the benefits of getting the large amount of work since 0.1 out >> > to the public. Release early/often, especially when you're in 0.x >> > versions. >> > >> > Concretely, let me propose we fix the two bugs open for 0.2, and mark >> > the rest as 0.3? >> > >> > http://issues.apache.org/jira/browse/MAHOUT-181 >> > http://issues.apache.org/jira/browse/MAHOUT-114 (is this a 'bug'?) >> >> MAHOUT-157 Frequent Pattern Mining using Parallel FP-Growth >> >> I think this should go in. Robin has made great progress and put in an >> updated patch late last week. I would love to thoroughly review said >> patch, but currently am unable to find time to do so. From what I >> looked at over the weekend, it does look good. Currently the status is: >> It implements a very fast, highly optimized serial version of the >> algorithm that I would love to see for 0.2. The parallel version than >> can go into 0.3. Sean, could you please have a closer look at the code >> to spot any problems that would block it from being committed? >> >> >> MAHOUT-165 Using better primitives hash for sparse vector for >> performance gains >> >> Judging from the comments, people are still working on it. >> >> MAHOUT-171 Move deployment to repository.apache.org >> >> I am fine if that is thrown out, yet the upcoming release would be a >> nice chance to test the setup. I would suggest to set a timebox for >> testing the changes - if it does not work out, move it on to 0.3 >> >> MAHOUT-138 Convert main() methods to use Commons CLI >> >> As there are quite a few methods that need changes I am fine with >> leaving the issue as is and moving it over to 0.3 until all is >> converted. >> >> MAHOUT-54 parallelize k-means sharing the predominance of canopies >> >> Judging from the comments this can savely be moved to 0.3 or even >> closed as won't fix. >> >> MAHOUT-78 HBase RowResult/BatchUpdate access via Mahout Vector >> interface >> >> Judging from the comments this can safely be moved to 0.3 or even be >> marked as won't fix. >> >> As for the other few issues, I cannot comment. >> >> Isabel >> > >
