You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mark Robert Miller (Jira)" <ji...@apache.org> on 2020/02/05 03:47:00 UTC
[jira] [Commented] (HBASE-23779) Up the default fork count to make
builds complete faster; make count relative to CPU count
[ https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030336#comment-17030336 ]
Mark Robert Miller commented on HBASE-23779:
--------------------------------------------
bq. More parallelism willl probably mean more test failure. Let me take a look see.
I'm going to convince you this is a good thing! But maybe not on main branches until it's a bit smooth.
> 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: Bug
> Components: test
> Reporter: Michael Stack
> Priority: Major
>
> 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)