rmuir commented on issue #11924: URL: https://github.com/apache/lucene/issues/11924#issuecomment-1312640064
Yes, for background I think the flag was added with docker usages in mind: https://bugs.openjdk.org/browse/JDK-8189497 But the idea is the same here. Since we're making the build go parallel with multiple jvms (e.g. 4), let's prevent from overwhelming the machine. For this issue i would suggest adding `-XX:ActiveProcessorCount=1` to: * `gradle/hacks/turbocharge-jvm-opts.gradle` * `gradle/testing/defaults-tests.gradle` * `help/localSettings.txt` This way, the many forked jvms that we spin up only have smaller number of compiler/gc threads/default threadpool sizes each. The issue is especially exacerbated by #11925, because we're still enabling things like C2 compiler there, so the many forked error-prone-monkey-patched-javac tasks all waste a ton of cpu for no good reason. But currently I don't have enough gradle kung-fu to figure out how to pass jvm args to the error-prone :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
