[
https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080016#comment-17080016
]
Michael Stack commented on HBASE-23779:
---------------------------------------
Ok. Just pushed subtask HBASE-24150. It adds -T2 to all mvn invocations. I
pushed it in favor of the patch that is here against this issue which doubles
the forkcount from 0.25C to 0.5C since in testing -- both here and locally --
it seems to give the biggest improvement in elapsed build times and is least
threatening to stability. Originally I was trying to do a combination of the
approaches upping forkcount and passing a fat -T value to mvn but seems to
destabilize.
I pushed on branch-2 only for now. Will study it. If all good, will push
everywhere.
> Up the default fork count to make builds complete faster; make count relative
> to CPU count
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-23779
> URL: https://issues.apache.org/jira/browse/HBASE-23779
> Project: HBase
> Issue Type: Task
> Components: test
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: Screen Shot 2020-04-08 at 9.19.53 AM.png,
> addendum2.patch, test_yetus_934.0.patch
>
>
> Tests take a long time. Our fork count running all tests are conservative --
> 1 (small) for first part and 5 for second part (medium and large). Rather
> than hardcoding we should set the fork count to be relative to machine size.
> Suggestion here is 0.75C where C is CPU count. This ups the CPU use on my box.
> Looking up at jenkins, it seems like the boxes are 24 cores... at least going
> by my random survey. The load reported on a few seems low though this not
> representative (looking at machine/uptime).
> More parallelism willl probably mean more test failure. Let me take a look
> see.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
