[Backgroundrb-devel] Behaviour of pool_size setting

[skaar]

* Christian Schlaefcke (cschlaefcke at wms-network.de) [070515 23:49]:
> Hi,
> 
> I have backgroundrb running to decouple the execution of massive 
> business logic from an ActionWebservice request. The service is designed 
> to take some configuration parameters and fire a lot of background 
> workers to do the requested work. Due to performance reasons I want to 
> limit the number of workers to a maximum number of 30. But when I start 
> a configuration that requires for example 300 worker executions I can 
> see that the limit of 30 workers is not kept and a number of about 180 
> worker processes are filling up my process list.

ok, I might look at adding a 'max_worker' configuration parameter as
something separate from the thread pool (which really just say something
about the MiddleMan, not the exisiting workers) - changing the pool_size
semantics could impact current installations.

/skaar



> 
> I start my workers like this:
> 
> key = MiddleMan.new_worker(:class => :execution_worker, :args => 
> {...some_args...})
> 
> 
> Why do I see so much more than my declared number of 30 workers? Am I 
> wrong somehow? How do I have to understand the behaviour of pool_size? 
> What happens when I have 30 workers working and the 31st, 32nd, ..., 
> 300th request to start a worker comes in?
> 
> Thanks & Regards!
> 
> Christian
> 


> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

-- 
----------------------------------------------------------------------
|\|\             where in the       |          s_u_b_s_t_r_u_c_t_i_o_n 
| | >===========  W.A.S.T.E.        |                  genarratologies 
|/|/    (_)     is the wisdom       |                  skaar at waste.org
----------------------------------------------------------------------