JTreg spawns java processes and uses all memory with CONCURRENCY=auto
jonathan.gibbons at oracle.com
Mon May 20 16:05:12 PDT 2013
... unless you have a big, or very big machine.
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
> 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.
> On May 20 2013, at 13:59 , Tomasz Kowalczewski wrote:
>> 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:
>> OpenJDK repository was cloned from http://hg.openjdk.java.net/jdk8/tl
>> and 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.
>> Tomasz Kowalczewski
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jtreg-use