[
https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082732#comment-17082732
]
Michael Stack commented on HBASE-23779:
---------------------------------------
!Screen Shot 2020-04-13 at 4.09.49 PM.png!
Hard to say what definitive improvement is. Changes went in after build #3589
in the diagram. Looking at the jdk8/hadoop2 column, before patch, tests were
taking 4hr25mins approx (Up to 5hrs... but could be as low as 4hrs). Post
patch, same column is about 3hrs 18mins on average. Thats about 25% difference?
Other columns are more erratic in their timings. Hopefully an improvement.
Resolving.
> 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, Screen Shot
> 2020-04-13 at 4.09.49 PM.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)
