search for: rssworker

...s instructed: script/plugin install svn://rubyforge.org//var/svn/backgroundrb rake backgroundrb:setup I started it with: rake backgroundrb:start In a model I make the call: MiddleMan.new_worker :class => :rss_worker In /lib/workers I have file rss_worker.rb, which contains the class: Class RssWorker < BackgrounDRb::Rails def do_work(args) ... end end It seems like I have everything setup right, but I get the following NameError: uninitialized constant RssWorker Any ideas? It''s probably something dumb, but I can''t seem to figure it out. -- Posted via http:...

Hi All, It might be lack of sleep, but I am struggling to accurately limit our pool size. It seems like I can specify it on the server with the -s command line option and also on the client via the YAML pool_size. Is that right? Which one wins? Our problem is that we are getting about 40 threads on each backgroundrb box and it''s flooring our db and each bgrb box. We want around 8.

Hello, I''m using the scheduler to create several reusable workers of the same type, .e.g., RSSWorker, so I can avoid the overhead of initializing new processes (as suggested by Ezra to my previous question). Creating new workers through the external yaml seems pretty straightforward, but my question is is there a way to call these workers without using the job key? Currently, to use these workers,...

...ou don''t want them to run concurrently since that may hog CPU resources. You would rather want tasks to be queued and be processed one after another easily. The simple solution for such tasks is to set thread pool size for worker to 1 and use thread_pool.defer { do_something } class RssWorker < BackgrounDRb::MetaWorker set_worker_name :rss_worker pool_size(1) end Now no matter how many requests you send to the worker, they all will be queued in a thread pool, but since thread pool is of size 1, only one of the task would run at a time. You don''t have t...