[
https://issues.apache.org/jira/browse/LUCENE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021595#comment-17021595
]
Robert Muir commented on LUCENE-9160:
-------------------------------------
Similar comparison: if you have a 16 cpu machine and only use 4 runners, i can
speed up your tests by spawning 12 background threads from the build: 12
threads that spend 80% of their time mining cryptocurrency and only 20% of
their time running tests.
You'd see a nice speedup, even though overall its wasting all of your
resources. And if you set test jvms to 16 you'd see that these background
threads only caused contention and slowed you down, because they are wasting
your CPU overall. This is what C2 compiler does in our tests :)
> override heap / jvm params for tests in gradle build
> ----------------------------------------------------
>
> Key: LUCENE-9160
> URL: https://issues.apache.org/jira/browse/LUCENE-9160
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: LUCENE-9160.patch, LUCENE-9160.patch
>
>
> Currently the gradle.properties that is generated lets you control the heap
> and flags for the gradle build jvms.
> But there is no way to control these flags for the actual forked VMs running
> the unit tests. For example, minHeap is hardcoded at 256m and maxHeap at
> 512m.
> I would like to change minHeap to 512m as well, for a fixed heap, and set
> some other jvm flags, such as {{-XX:+UseParallelGC}} so that my tests are not
> slow for silly reasons :)
> I think it is stuff jenkins CI would need as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
