JTreg spawns java processes and uses all memory with CONCURRENCY=auto
Alan.Bateman at oracle.com
Wed May 22 09:43:23 PDT 2013
On 22/05/2013 16:36, Jonathan Gibbons wrote:
> Thanks for the feedback; I'll incorporate it later today.
> The other section I thought to add as I was driving home last night
> was a section on writing tests with concurrency in mind. For example,
> we have one langtools test that can utilize all the processors by
> itself. I'll add some notes on that aspect. That brings up a
> doc-design issue. There's a similar page I would like to write on
> choosing the best execution mode, and again, there are two potential
> audiences: those running jtreg, and those writing tests for jtreg. So
> the question is, how to organize notes like this, given the
> potentially different audiences?
> -- Jon
In addition to tests that uses all hw threads are tests that just can't
run concurrently with other tests in the area. We have a few cases in
the jdk repository where we have to use exclusiveAccess.dirs.
More information about the jtreg-use