Hi, I am trying to limit the number of worker threads running at the same time. Adding ":poolsize: 2" to backgroundrb.yml or starting backgroundrb server like this script/backgroundrb start -- -s 2 does not seem to help. I can still create more than 2 worker threads from a rails app. I tried this on ubuntu dapper - ruby 1.8.4 - backgroundrb 0.2.1 as well as mac osx 10.4.9 - ruby 1.8.5 - backgroundrb 0.2.1 but no luck. Does thread pool work for anyone properly? Or do you use some other methods like implementing your own queue system? Appreciate any hints. Thanks! cheers, mengkuan
I thought the parameter was :pool_size (not :poolsize), but either way, I''ve found it does not limit the number of slave processes spawned in backgroundrb. On 3/29/07, Meng Kuan <mengkuan at gmail.com> wrote:> > Hi, > > I am trying to limit the number of worker threads running at the same > time. Adding ":poolsize: 2" to backgroundrb.yml or starting > backgroundrb server like this > > script/backgroundrb start -- -s 2 > > does not seem to help. I can still create more than 2 worker threads > from a rails app. > > I tried this on > > ubuntu dapper > - ruby 1.8.4 > - backgroundrb 0.2.1 > > as well as > > mac osx 10.4.9 > - ruby 1.8.5 > - backgroundrb 0.2.1 > > but no luck. > > Does thread pool work for anyone properly? Or do you use some other > methods like implementing your own queue system? > > Appreciate any hints. Thanks! > > cheers, > mengkuan > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070329/39d225f7/attachment-0001.html
On 30 Mar 2007, at 6:26 AM, Mason Hale wrote:> I thought the parameter was :pool_size (not :poolsize), but either > way, I''ve found it does not limit the number of slave processes > spawned in backgroundrb.Yes, sorry about the typo. And yes, it does not seem to affect the spawning. So it seems I will be better off implementing my own queueing system?
It may be quicker to fix the existing queuing system in backgroundrb rather than implement something new. But I don''t know the details of the existing implementation. Skaar? Ezra? any suggestions? Mason On 3/29/07, Meng Kuan <mengkuan at gmail.com> wrote:> > On 30 Mar 2007, at 6:26 AM, Mason Hale wrote: > > > I thought the parameter was :pool_size (not :poolsize), but either > > way, I''ve found it does not limit the number of slave processes > > spawned in backgroundrb. > > Yes, sorry about the typo. And yes, it does not seem to affect the > spawning. So it seems I will be better off implementing my own > queueing system? > > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070329/cf2f7755/attachment.html