[concurrency-interest] Performance regression in newest (6/20/2013) jsr166 update

Doug Lea dl at cs.oswego.edu
Tue Jun 25 20:03:54 EDT 2013

On 06/22/13 20:42, Ron Pressler wrote:
> A couple of months ago I described the behavior detailed in the email exchange
> below. The newest update causes a slowdown of about 25% of this benchmark:
> ...

>      static ForkJoinPool fjPool = new ForkJoinPool(PARALLELISM,
> ForkJoinPool.defaultForkJoinWorkerThreadFactory, null, true);

Yes, some handling for pools run in async mode (which is not common)
got a little worse in the course of improving vastly more common cases.
Most of this can be reinstated though, which on a quick check of
a quick touch-up recovers performance on your test case. Stay tuned.


More information about the Concurrency-interest mailing list