You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Aditya Kishore (JIRA)" <ji...@apache.org> on 2015/05/15 00:39:00 UTC

[jira] [Commented] (DRILL-2039) use forks-per-CPU units in forkCount

    [ https://issues.apache.org/jira/browse/DRILL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544504#comment-14544504 ] 

Aditya Kishore commented on DRILL-2039:
---------------------------------------

It is causing trouble on my MacBook with 16 logical cores and 16GB of RAM. Half of the forked tests are killed immediately by OS for lack of memory.  

> 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)