On 11/12/2013 19:50, Jonathan Gibbons wrote:
:
I notice in your commands, you do NOT limit the amount of memory for
each JVM with -Xmx. That leaves all your JVMs using default
ergonomics, which may be unduly optimistic when you have lots of JVMs
running.
Yes, this is very important then running the jdk tests with
-concurrency. The :jdk_core and :jdk_svc tests are okay with
-vmoption:-Xmx256m, I have not tried anything smaller myself.
One thing that some of us don't have a handle on is the maximum number
of VMs that are in use during a test run. It's something that Mike and I
were chatting about recently [1]. In any case, it's the maximum number
of VMs (and thus the memory) that really limits the concurrency. Many of
the tests are not compute bound so you can push the concurrency (but
only if you have the memory to do it).
One other thing to say about concurrency that auto just doesn't work on
SPARC, just too many hardware threads.
-Alan.
[1]
http://mail.openjdk.java.net/pipermail/jtreg-use/2013-November/000305.html
