You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Daniel Barclay (Drill) (JIRA)" <ji...@apache.org> on 2015/05/15 01:19:59 UTC

[jira] [Commented] (DRILL-3089) Revert to 4 forked test and allow override from command line

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

Daniel Barclay (Drill) commented on DRILL-3089:
-----------------------------------------------

Why don't we have the known-reliable value of "1" in the checked-in version, and let people who want to optimize run time risk problems on their own machines? Since they consciously changed forkCount, if they run into problems because of that forkCount setting, they're likely to recognize the problem easily.

Right now, people who want to optimize run time risk problems on _other_ people's machines (by having the non-unity value of forkCount checked in). Those other people, not having consciously set forkCount, aren't going to easily recognize that timeouts on their machines are because of the forkCount setting.


> Revert to 4 forked test and allow override from command line
> ------------------------------------------------------------
>
>                 Key: DRILL-3089
>                 URL: https://issues.apache.org/jira/browse/DRILL-3089
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Aditya Kishore
>            Assignee: Aditya Kishore
>
> The current, one forked test per CPU core, can be quite resource intensive on modern machines with 8-16 cores (See discussion on DRILL-2039).
> We should revert to 4 forked test by default and allow overriding this from command line.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)