[
https://issues.apache.org/jira/browse/LUCENE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022352#comment-17022352
]
Robert Muir commented on LUCENE-9160:
-------------------------------------
Dawid I opened LUCENE-9165 to discuss further.
Also keep in mindthis jira ticket alters the defaults in ways that impact this.
For example, when running lucene tests with 3 VMs I see load average around 4.0
instead of 15.0-16.0 before this very patch was committed!
That's because I don't have 3 CICompiler threads *per* JVM doing a lot of
useless C2 recompilation. So it makes things more efficient and I think we
should raise the hard cap of 4 jvms to 8 or 12.
> 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
