<div dir="ltr">Thank you for explaining. Is JDK-<span style="font-family:Helvetica;font-size:12px">8014819 visible on publicly available bug tracker?</span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 1:05 AM, Jonathan Gibbons <span dir="ltr"><<a href="mailto:jonathan.gibbons@oracle.com" target="_blank">jonathan.gibbons@oracle.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>... unless you have a big, or very big
machine.<br>
<br>
-- Jon<div><div class="h5"><br>
<br>
<br>
On 05/20/2013 04:02 PM, Mike Duigou wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">The biggest issue with any concurrency auto or a
specific number in practice seems to be that VMs are not provided
a maximum size and are dependent upon the default "VM ergonomics"
sizing. With default sizing, on most machines you will run out
memory before you run out of cores.
<div><br>
</div>
<div>There's a current effort (JDK-<span style="font-family:Helvetica;font-size:12px">8014819) </span>to
specify a default VM size to be used by the test vm instances
which should help things. For the moment I wouldn't suggest
using more than CONCURRENCY=4.
<div><br>
</div>
<div>Mike<br>
<div><br>
<div>
<div>On May 20 2013, at 13:59 , Tomasz Kowalczewski wrote:</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hello,<br>
<br>
</div>
during a recent "Adopt OpenJDK" event held in Krakow
I was using jtreg for running OpenJDK test cases. It
was set up as per instructions published here: <a href="https://java.net/projects/adoptopenjdk/pages/InstallJtreg" target="_blank">https://java.net/projects/adoptopenjdk/pages/InstallJtreg</a><br>
<br>
</div>
OpenJDK repository was cloned from <a href="http://hg.openjdk.java.net/jdk8/tl" target="_blank">http://hg.openjdk.java.net/jdk8/tl</a>
and jtreg version was
jtreg-4.1-bin-b05_29_nov_2012.zip<br>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
</div>
<div>I have set 'CONCURRENCY=auto'
environment variable.<br>
<br>
</div>
<div>When running a test suite (.e.g.: 'cd
jdk8_tl/test; make jdk_util') jtreg
spawns a lot of java processes and it
seems not to stop. Ever. It uses all 8
GB of RAM on my machine at which point
Windows starts killing random processes.<br>
<br>
</div>
<div>With 'CONCURRENCY=1' jtreg will spawn
only a few java processes and will
happily run all the test.<br>
<br>
</div>
<div>What is the behavior for
'CONCURRENCY=auto'? Which value is used
as default? Maybe it is not a bug its
just that OpenJDK tests should be run on
a big server machine with lots of RAM?<br>
</div>
<div><br>
</div>
<div>Any suggestions or pointers to
documentation will be very appreciated.<br>
<br>
</div>
<div>-- <br>
Regards,<br>
Tomasz Kowalczewski
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Tomasz Kowalczewski
</div>