<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11/12/2013 19:50, Jonathan Gibbons wrote:
<blockquote cite="mid:52A8C208.3080806@oracle.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
:<br>
<br>
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.<br>
</blockquote>
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.<br>
<br>
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).<br>
<br>
One other thing to say about concurrency that auto just doesn't work
on SPARC, just too many hardware threads.<br>
<br>
-Alan.<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://mail.openjdk.java.net/pipermail/jtreg-use/2013-November/000305.html">http://mail.openjdk.java.net/pipermail/jtreg-use/2013-November/000305.html</a><br>
<br>
<br>
</body>
</html>