Re: [Proxool-developer] Threads when using a lot of pools

[Martin C. <mus...@us...>]

Just an old post that I might as well respond too..

 > At the moment it is hard coded to just one thread for house keeping and
 > prototyping, but it would be easy to increase that. I wonder how we
 > should decide how many threads to have?


The question is how much "housekeeping" do these threads do? Two threads 
seem reasonable. I imagine that housekeeping isn't a real high priority 
(esspecially around my house it seems;), so why bloat the memory 
footprint just to clean up a few connections sooner.

 > Or we could do some measurements. Work out how much idle time the
 > threads have and only start a new thread if the existing threads aren't
 > coping.


Perhaps keeping a small pool of management threads would make sense, and 
then have one that manages their dispatch. Again though probably not a 
big deal. Threads are memory hogs, and if you can limit them more the 
better.

Martin