[concurrency-interest] Class striped/ordered Thread Pool

√iktor Ҡlang viktor.klang at gmail.com
Sat May 12 08:35:46 EDT 2012

It'll only be an issue if you have arbitrary stripes. Fixing that is a
great exercise to the reader!

On May 12, 2012 1:55 PM, "Aleksey Shipilev" <aleksey.shipilev at gmail.com>

> On Sat, May 12, 2012 at 2:09 PM, √iktor Ҡlang <viktor.klang at gmail.com>
> wrote:
> > Here's an implementation I threw together (haven't been tested yet so
> > that should make any Executor into a striped one, for every runnable
> that is
> > put in there which is Striped.
> >
> > https://gist.github.com/2665603
> Neat trick, but it is prone to memory leaks. You will have to protect
> yourself from multiple stripe classes come and go, that is, there is a
> garbage buildup in $stripes map, if some stripes are not being used
> (from some point, forever). Getting that right in race-free manner is
> tough.
> -Aleksey.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20120512/5db7a1e5/attachment.html>

More information about the Concurrency-interest mailing list