[
https://issues.apache.org/jira/browse/DRILL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544529#comment-14544529
]
Daniel Barclay (Drill) commented on DRILL-2039:
-----------------------------------------------
I think the default should be 1.
That would default to the most reliable value, and problems would show up only
when one tries to optimize (parallelizing to reduce elapsed time) beyond one's
machine's capabilities.
(Relatedly, does anyone know how to override the forkCount value from the
command line? (I and someone else have tried some command-line option that was
supposed to work but didn't actually seem to work.))
> use forks-per-CPU units in forkCount
> ------------------------------------
>
> Key: DRILL-2039
> URL: https://issues.apache.org/jira/browse/DRILL-2039
> Project: Apache Drill
> Issue Type: Improvement
> Components: Tools, Build & Test
> Reporter: Daniel Barclay (Drill)
> Assignee: Hanifi Gunes
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: DRILL-2039.1.patch.txt, DRILL-2039.2.patch
>
>
> Can Surefire's fork count be set using units of forks per CPU instead of the
> absolute number of forks (i.e., {{<forkCount>1C</forkCount>}} instead of
> {{<forkCount>4</forkcount>}})?
> That would let developers with more powerful machines still run tests in
> parallel while letting others avoid or reduce test timeout errors without the
> risk of forgetting to re-edit pom.xml after every switch to a different git
> branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
