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.

With some rebalancing/adjustments to our test landscape the issues are gone. 
Unfortunately there was not much interest  in the resource related discussion on jtreg-dev  
https://mail.openjdk.org/pipermail/jtreg-dev/2024-February/001926.html

closing for now because the issues are currently not seen any more on our side.

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

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