JTreg spawns java processes and uses all memory with CONCURRENCY=auto

[Tomasz Kowalczewski]

Thank you for explaining. Is JDK-8014819 visible on publicly available bug
tracker?


On Tue, May 21, 2013 at 1:05 AM, Jonathan Gibbons <
jonathan.gibbons at oracle.com> wrote:

>  ... unless you have a big, or very big machine.
>
> -- Jon
>
>
>
> On 05/20/2013 04:02 PM, Mike Duigou wrote:
>
> 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.
>
>  There's a current effort (JDK-8014819) 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.
>
>  Mike
>
>  On May 20 2013, at 13:59 , Tomasz Kowalczewski wrote:
>
>   Hello,
>
>  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: https://java.net/projects/adoptopenjdk/pages/InstallJtreg
>
>  OpenJDK repository was cloned from http://hg.openjdk.java.net/jdk8/tland jtreg version was jtreg-4.1-bin-b05_29_nov_2012.zip
>
>  I have set 'CONCURRENCY=auto' environment variable.
>
>  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.
>
>  With 'CONCURRENCY=1' jtreg will spawn only a few java processes and will
> happily run all the test.
>
>  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?
>
>  Any suggestions or pointers to documentation will be very appreciated.
>
>  --
> Regards,
> Tomasz Kowalczewski
>
>
>
>


-- 
Tomasz Kowalczewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20130521/4947acf2/attachment-0001.html