Integrated: 8267246: -XX:MaxRAMPercentage=0 is unreasonable for jtreg tests on many-core machines

Jie Fu jiefu at openjdk.java.net
Wed May 19 01:51:43 UTC 2021


On Mon, 17 May 2021 13:24:16 GMT, Jie Fu <jiefu at openjdk.org> wrote:

> Hi all,
> 
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
> 
> It can be reproduced by: `make test TEST="vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java" JTREG="JOBS=26"` on almost all machines.
> 
> Setting `-XX:MaxRAMPercentage=0` on many-core machines seems unreasonable.
> It would be better to fix it.
> 
> Thanks.
> Best regards,
> Jie
> 
> 
> [1] https://github.com/openjdk/jdk/blob/master/make/RunTests.gmk#L741

This pull request has now been integrated.

Changeset: 0daec497
Author:    Jie Fu <jiefu at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/0daec497fea8c048a9455e4ff331a9d8c4293a4b
Stats:     1 line in 1 file changed: 0 ins; 0 del; 1 mod

8267246: -XX:MaxRAMPercentage=0 is unreasonable for jtreg tests on many-core machines

Reviewed-by: shade, erikj

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

PR: https://git.openjdk.java.net/jdk/pull/4062



More information about the build-dev mailing list