[concurrency-interest] ThreadPoolExecutor workQueue concurrencyissue
dcholmes at optusnet.com.au
Tue Dec 11 04:15:17 EST 2007
How do you define "some kind of fairness" ?
When staged/pipelined designs start to saturate like that, you might see if
you can duplicate the stages to achieve greater parallelism.
From: concurrency-interest-bounces at cs.oswego.edu
[mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of Guy Korland
Sent: Tuesday, 11 December 2007 5:40 PM
To: concurrency-interest at cs.oswego.edu
Subject: [concurrency-interest] ThreadPoolExecutor workQueue
We built an application in a SEDA fashion, working in stages from one
ThreadPool to another.
We found out that the BlockingQueue used by the ThreadPoolExecutor became
a major concurrency killer when we start working on 4 cores machines and
The thing is that we don't really need the strong FIFO behavior forced by
all the BlockingQueue implementations available, some kind of fairness will
be good enough.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest