First, some good news: after a few fits, starts, and configuration tweaks, we''ve succeeded in deploying BackgrounDRb onto our production machines, where we''re using itto perform cache expiration on our Rails generated pages. [We''re using v1.0.1 code at the moment, but plan to upgrade to 1.0.3 in the next week or two.] We use an event driven model for expiration, which is triggered by observers in our Rails application. However, we''re concerned about robustness, and would like to set up some monitoring tools. In particular, we''d like to keep tabs on things like: * total number of threads allocated * number of active worker threads * duration of currently active threads (to help identify hung ones) Are there any good examples of monitor workers that do this now? What sort of statistics API''s are available? I didn''t see anything obvious in the RDoc for this. Thanks, George George Feil | Senior Software Engineer office 415.295.8524 | fax 415.295.8580 www.realgirlsmedia.com www.divinecaroline.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080215/45a6b735/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 3238 bytes Desc: image001.jpg Url : http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080215/45a6b735/attachment-0001.jpe
I don''t know if there are any API''s, but you could create a monitoring/ stats worker that exposes whatever data you can gather. If you write one, please consider submitting it for inclusion in the project. Alex On Feb 15, 2008, at 9:24 AM, George Feil wrote:> First, some good news: after a few fits, starts, and configuration > tweaks, we?ve succeeded in deploying BackgrounDRb onto our > production machines, where we?re using itto perform cache expiration > on our Rails generated pages. [We?re using v1.0.1 code at the > moment, but plan to upgrade to 1.0.3 in the next week or two.] We > use an event driven model for expiration, which is triggered by > observers in our Rails application. > > However, we?re concerned about robustness, and would like to set up > some monitoring tools. In particular, we?d like to keep tabs on > things like: > > total number of threads allocated > number of active worker threads > duration of currently active threads (to help identify hung ones) > > Are there any good examples of monitor workers that do this now? > What sort of statistics API?s are available? I didn?t see anything > obvious in the RDoc for this. > > Thanks, > George > > <image001.jpg> > George Feil | Senior Software Engineer > office 415.295.8524 | fax 415.295.8580 > www.realgirlsmedia.com > www.divinecaroline.com<_______________________________________________ > 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/20080215/8f042d34/attachment-0001.html
On Feb 15, 2008 12:24 PM, George Feil <gfeil at realgirlsmedia.com> wrote:> Are there any good examples of monitor workers that do this now? What sort > of statistics API''s are available? I didn''t see anything obvious in the RDoc > for this. >George, I have been using god (god.rubyforge.org) for this purpose with great success. Good luck. John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080216/561f4dab/attachment.html
2008/2/15 George Feil <gfeil at realgirlsmedia.com>:> > > > > First, some good news: after a few fits, starts, and configuration tweaks, > we''ve succeeded in deploying BackgrounDRb onto our production machines, > where we''re using itto perform cache expiration on our Rails generated > pages. [We''re using v1.0.1 code at the moment, but plan to upgrade to 1.0.3 > in the next week or two.] We use an event driven model for expiration, which > is triggered by observers in our Rails application. > > > > However, we''re concerned about robustness, and would like to set up some > monitoring tools. In particular, we''d like to keep tabs on things like: > > > > total number of threads allocated > number of active worker threads > duration of currently active threads (to help identify hung ones) > > > > Are there any good examples of monitor workers that do this now? What sort > of statistics API''s are available? I didn''t see anything obvious in the RDoc > for this. > >Its not there, right now. but should be pretty easy to implement.