[
https://issues.apache.org/jira/browse/MAHOUT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760890#action_12760890
]
Robin Anil commented on MAHOUT-170:
-----------------------------------
A Quick Test, uses some parameters which i felt would improve performance.
Running FPGrowth on 340K transactions trying to fetch top 50 closed patterns
each of the 360 features
Max Heap set at 2GB, Heap used 400-500MB
run with -server option
Here is the log of the test in order
1. adding -XX:+AggressiveOpts: decreased total running time by about 30s (3:10
v 3:40) and Yourkit reports cpu time decreased from 2:48 to 2:38
2. adding -XX:+UseFastAccessorMethods Runtime 2:54, YourKit reports CPU time
as 2:36
3. adding -Xmn1024M (increased the heap size for young generation to improve GC
for shortlived objects) Thrashing occurred
-Xmn128M No thrashing this time runtime increased to 3:45 CPU
time 3:10
removed -Xmn option
4. adding -Xss 128K reduced the execution stack size. Runtime and cpu time
increased slightly (5-7 sec) from (2)
5. adding -XX:ParallelGCThreads=20 Again Runtime and cpu time increased by
about 10-15 secs from (2)
Moral 1: Dont mess around unless you know what you are doing
Moral 2: -server -XX:+AggressiveOpts -XX:+UseFastAccessorMethods gives
significant boost to the runtime
> Enable Java compile optimize flag during build
> ----------------------------------------------
>
> Key: MAHOUT-170
> URL: https://issues.apache.org/jira/browse/MAHOUT-170
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.2
> Reporter: Robin Anil
> Attachments: optimize.patch
>
>
> in maven compile plugin enable optimize=true flag
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
