[
https://issues.apache.org/jira/browse/MAHOUT-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675649#comment-13675649
]
Sean Owen commented on MAHOUT-916:
----------------------------------
I think the full and intended config here is:
<forkCount>X</forkCount>
<threadCount>1</threadCount>
<perCoreThreadCount>false</perCoreThreadCount>
<reuseForks>false</reuseForks>
<parallel>classes</parallel>
.. and the question is just what X is. This makes sure that a fresh JVM is used
for each test class, which is necessary to fully isolate RNGs I believe.
But even at X=2 I still get a system that is completely pegged on I/O once the
Hadoop-related jobs start. I am not sure even the minimal parallelism is usable.
(I have a 2-core Intel i7 2.66GHz Macbook with 8GB RAM and a 5400rpm drive.
It's not a memory issue and it's not a weak machine)
Does this mirror anyone else experience?
> Make Mahout's tests run in parallel
> -----------------------------------
>
> Key: MAHOUT-916
> URL: https://issues.apache.org/jira/browse/MAHOUT-916
> Project: Mahout
> Issue Type: Improvement
> Components: build
> Reporter: Grant Ingersoll
> Assignee: Isabel Drost-Fromm
> Priority: Minor
> Labels: MAHOUT_INTRO_CONTRIBUTE
> Fix For: 0.8
>
> Attachments: MAHOUT-916.patch, MAHOUT-916.patch, MAHOUT-916.patch,
> MAHOUT-916.patch
>
>
> Maven now supports parallel execution of tests. We should hook this in to
> Mahout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
