drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hanifi Gunes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-2039) use forks-per-CPU units in forkCount
Date Thu, 09 Apr 2015 18:53:13 GMT

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

Hanifi Gunes commented on DRILL-2039:

We have tried on multiple machines with 1C option. It does not seem to cause timeouts except
I/O intensive tests(TestWriteToDisk etc) whose timeout intervals are individually lifted up.

> 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

View raw message