Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
* defaulting all concurrency models to 50 connections?
@ 2011-04-25 23:40 Eric Wong
       [not found] ` <20110425234044.GA21884-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Wong @ 2011-04-25 23:40 UTC (permalink / raw)
  To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw

I figure the defaults for Rainbows! sucks badly for everyone anyways,
maybe it's just easier to make ThreadPool, ThreadSpawn,
WriterThreadPool, and WriterThreadSpawn use the same defaults as
everyone else.  It'd still suck, but at least it'd suck more
consistently :)

I suspect people are most likely to be quietly experimenting with
ThreadSpawn/ThreadPool since they're the most conservative of the
available options (besides Base), but is anybody relying on the low (30,
20 respectively) defaults?

(You don't have to say where you're testing/experimenting with it and I
don't care if you use a fake name or not)

I'm not sure about the cost of native threads on other platforms, but
NPTL on Linux is pretty cheap with MRI 1.9, especially if you're on
64-bit.

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: defaulting all concurrency models to 50 connections?
       [not found] ` <20110425234044.GA21884-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
@ 2011-04-26  1:07   ` ghazel-Re5JQEeQqe8AvxtiuMwx3w
  0 siblings, 0 replies; 2+ messages in thread
From: ghazel-Re5JQEeQqe8AvxtiuMwx3w @ 2011-04-26  1:07 UTC (permalink / raw)
  To: Rainbows! list

I'm testing with ThreadSpawn at 100 workers on REE 1.8.7, but I by no
means hit anywhere near that number of actual simultaneous
connections.

-Greg

On Mon, Apr 25, 2011 at 4:40 PM, Eric Wong <normalperson@yhbt.net> wrote:
> I figure the defaults for Rainbows! sucks badly for everyone anyways,
> maybe it's just easier to make ThreadPool, ThreadSpawn,
> WriterThreadPool, and WriterThreadSpawn use the same defaults as
> everyone else.  It'd still suck, but at least it'd suck more
> consistently :)
>
> I suspect people are most likely to be quietly experimenting with
> ThreadSpawn/ThreadPool since they're the most conservative of the
> available options (besides Base), but is anybody relying on the low (30,
> 20 respectively) defaults?
>
> (You don't have to say where you're testing/experimenting with it and I
> don't care if you use a fake name or not)
>
> I'm not sure about the cost of native threads on other platforms, but
> NPTL on Linux is pretty cheap with MRI 1.9, especially if you're on
> 64-bit.
>
> --
> Eric Wong
> _______________________________________________
> Rainbows! mailing list - rainbows-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rainbows-talk
> Do not quote signatures (like this one) or top post when replying
>
_______________________________________________
Rainbows! mailing list - rainbows-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-04-26  1:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-25 23:40 defaulting all concurrency models to 50 connections? Eric Wong
     [not found] ` <20110425234044.GA21884-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-04-26  1:07   ` ghazel-Re5JQEeQqe8AvxtiuMwx3w

Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).