RFR: JDK-8324930: java/lang/StringBuilder problem with concurrent jtreg runs

[Jaikiran Pai]

On Tue, 30 Jan 2024 09:08:28 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

> On some Windows machines we see sometimes OOM errors because of high resource (memory/swap) consumption. This is especially seen when the jtreg runs have higher concurrency. A solution is to put the java/lang/StringBuilder tests in the exclusiveAccess.dirs group so that they are not executed concurrently, which helps to mitigate the resource shortages.
> Of course this has the downside that on very large machines the concurrent execution is not done any more.

Hello Matthias,

> What do you think about marking jtreg tests with higher memory requirements with a jtreg key like highmemusage ?

I still don't have any concrete suggestions - it isn't fully clear to me what we should do here. Part of the reason is because, details like the exact command that's being used to run these tests, the "-concurrency" that's either getting computed or explicitly set, the exact Windows OS version and Windows system configurations like the total memory available, the number of CPUs etc... are all unknown right now. Having those details I think would be good to understand what approach to take here. Those details will also help understand why this isn't observed in our internal CI runs.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17625#issuecomment-1952463101