From: Ezra Zygmuntowicz Date: 2007-05-28T05:52:05+09:00 Subject: Re: BackgrounDRb Theory On May 27, 2007, at 12:01 PM, brabuhr@gmail.com wrote: > On 5/27/07, Sy Ys wrote: >> I'm making a site which allows subscribers to scrape their unnamed >> social network profile for changes regularly using BackgrounDrb. I >> can: >> >> A) Create 1 worker which will update all subscriber profiles at >> once. I >> like this because its simple. I don't like this because it will >> create a >> server-intensive traffic spike. >> >> B) Instantiate a new worker which will run every 24 hours after a >> person >> signs up. I like this because it eliminates the spike but still >> updates >> everyone. But I'm not sure what effect having an worker running >> for each >> user will have on server memory. >> >> C) Other? > > C) Create a pool of n workers which will pull jobs from a queue (maybe > also look at something like Ruby Queue[1]). > > [1] http://codeforpeople.com/lib/ruby/rq/rq-3.1.0/ > Yeah I have the best luck with backgroundrb when I run a set number of immortal workers that just loop and pull jobs from a queue. Cheers- -- Ezra Zygmuntowicz -- Lead Rails Evangelist -- ez@engineyard.com -- Engine Yard, Serious Rails Hosting -- (866) 518-YARD (9273)