[Nightly] Attempt to temporarily fix nightly gradle heap JVM out of mem thrashing. #3785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to try this as an experiment to see what impact it has on the nightly. I suspect it could be a temporary fix for the Gradle JVM heap out of memory and thrashing errors that preventing nightly builds from succeeding while continuing investigation to a correct fix.
By default Gradle will use a max number of workers equal to the number of logical processors available. Multiple workers could be competing for available heap space and starving each other out. This should prevent that but at the cost of longer build times.
If build times are too long, it might be required to specify a larger heap space for Gradle to use while increasing the max number of workers to something that makes sense.