I never replied to this! Sorry!
Threadpooled mode does improve the spinup time of threads under JRuby,
but I've realized lately most of that benefit could be realized by
pooling ThreadContext instances instead. The threadpool implementation
for Ruby threads just seems to introduce complexity, and
We fire quite a few (one or two per second) short-lived threads in our thick
clients, and we are planning to try thread-pooled mode in a week or so. The
description of thread-pooled mode promises performance improvement when using
short-lived threads. Still true?
Uwe
On Apr 23, 2010, at 2:57
I actually did have a putative use case for threadpool mode, but that use
case itself turned out to be more trouble than it was worth :-)
On Fri, Apr 23, 2010 at 8:57 AM, Charles Oliver Nutter
wrote:
> I added it a long time ago
> intending to make it solid for all uses, but I don't think anyone
Looks like the improvements I committed last night to eliminate
RubyThread leakage have caused the threadpool mode to break:
http://ci.jruby.org/job/jruby-test-all/126/console
I'll look at fixing that today, but I have to ask: is anyone using or
interested in using threadpooled mode? I added it a
