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

[Matthias Baesken]

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, any further comments on this ?
Or should we carry the discussion to jtreg on how to work with resource (in this case memory) issues in case of concurrent runs ?
Can we **_configure_** to execute some jtreg tests with higher mem requirements with less concurrency ?

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

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