Displaying 20 results from an estimated 6000 matches similar to: "pool_size"
2007 May 15
6
Behaviour of pool_size setting
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
2007 Apr 26
2
looking for a worker that''s gone
In my app, I store the job key when a worker is fired off and then
check back in periodically to see how its doing. The workers delete
themselves when they''re done. I would expect when I try to get a
worker that has been deleted, I would get nil or a proper exception,
but instead I get:
>> MiddleMan.worker(''foobar'')
NoMethodError: undefined method
2008 Jan 03
1
Thread_pool bug?
I have a previous question regarding long tasks and the thread_pool (sorry
for the dup, I didn''t see the first go through). To try and track things
down, I made a change based on a suggestion found in the archives. I moved
my import contacts worker to its own file and set the pool_size to 1.
class ImportContactsWorker < BackgrounDRb::MetaWorker
set_worker_name
2007 May 31
0
Slave socket problem again
Hello!
I have been using backgroundrb for a small project. My worker task is
run every minute, checks the processing queue in data-base and execute
the business method from Rails if something is to be done.
Unfortunately I was hit by the problem of backgroundrb server dying
after some runs. The exception is:
20070531-11:06:05 (31816) Starting worker: s_e_work sql_exe
(s_e_work_sql_exe) ()
2007 Jun 21
0
config file questions
example:
:host: 192.168.1.101
:protocol: druby
:worker_dir: lib/workers
:rails_env: production
:pool_size: 15
:load_rails: true
:timer_sleep: 60
:acl:
:deny: all
:allow: localhost 192.168.1.*
:order: deny allow
I have this config file on 2 app servers running rails. The 2 servers are
running behind a load balancer. I''m starting the backgroundrb server on the
one server with the
2007 Apr 28
1
backgroundrb and fastthread
I was just curious if anyone noticed any significant performance
improvements using fastthread (or Ruby 1.8.6) with BackgrounDRb
Brandon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url :
2007 Oct 12
0
Trouble on Multi Server setup
Hello all,
I''m having some trouble getting backgroundrb set up so that all the
processing happens on a single machine. I have 3 load balanced
machines. Right now, all three run our web application and create
MiddleMan workers to generate a large PDF report.
However, because of the processing power needed to generate the PDFs,
I want to change our setup so that two servers run
2006 Dec 08
3
Thread Pool Size?
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.
2007 May 09
0
Neophyte needs help!
Hi All,
Real neophyte here, to both backgroundrb and ruby/rails in general.
(Hey, we''ve all got to start somewhere, right!) :)
I''ve just been playing around with the example code at
http://backgroundrb.rubyforge.org/ , and trying to get all
the pieces to work (btw, I''m using version 0.2.1).
I did a ''generate worker example'', which created an
2008 Jan 13
3
right usage of bdrb
Hi,
i''m going to implement a syndication-service, which will get lists in
xml with some meta-data an enclosed video files, which will get encoded
at the end. The syndication run will be startet every five minutes of
a full hour.
So i thought to build 4 Worker. One for checking which feeds to
syndicate (syndication_worker) at a specific time, one for processing
the list
2008 May 20
1
Couple questions on BDRb and concurrent processing
My Rails site uses BackgroundDRb and I have a couple of questions:
1. Can someone point me to some sample code/examples for how to use
thread_pool? The website doc says to add a line
======
pool_size 10
======
in my Worker class which seems straightforward.
I wasn''t able to understand this part though:
=========
thread_pool.defer(wiki_scrap_url) { |wiki_url| scrap_wikipedia(wiki_url) }
2006 Dec 04
4
Question about acls
Hi,
I''m not much of a developer but I''ve been using backgroundrb for a
while now and with the release of 0.2.1 it looks like I can finally
upgrade from the old version (0.2.0 had some weird issues when jobs
just wouldn''t run, seems to have cleared up now - Thanks!).
Anyhow, while I''m doing this, I would like to tackle this problem.
Most tasks I run in
2007 Dec 23
0
Updates and Fixes and more of awesome stuff
1. Whenever you ask BackgrounDRb to perform a particular task using:
MiddleMan.ask_work(:worker => :rss_worker,:worker_method =>
:fetch_url, :data => "www.google.com")
Your task would be performed then and there. But, if your worker is
busy, task won''t be queued, except in socket buffer.
And your request may get lost. This isn''t generally a problem
2008 May 09
1
register_status for excess thread_pool?
Hi,
Newbie here. I''ve got a worker (for generating PDF reports) that
uses the "thread_pool" to allow processing multiple reports
simultaneously and queue up any requests that exceed the thread
pool (pool_size = 10 currently).
def process_pdf(user)
thread_pool.defer(user) do |user|
makepdf(user)
end
end
My question is: I use a mutex to handle
2007 May 15
4
Need help with singleton worker
We have a fairly expensive task that we''d rather not schedule too many
instances of in parallel.
Couldn''t get pool_size to limit the amount of workers, and I figure
that''s hardly optimal anyway, so would like to have the work queued up
for a single named worker instead, running as soon as possible.
Using MiddleMan.schedule_worker() with :job_key does start off a
2007 Nov 14
7
BackgrounDRb version 1.0RC1 available now
Hi Folks,
BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be
used with Ruby on Rails applications for offloading long-running tasks.
Since a Rails application blocks while serving a request it is best to
move long-running tasks off into a background process that is divorced
from http request/response cycle.
This new release of BackgrounDRb is also modular and can be used
2007 Jun 06
2
struggling with stability
Greetings all,
Unit tests are passing, but I''m having mucho problems getting brb to
run without exceptions for more than 6 hours.
I''m seeing a mixture of the following 2 exceptions:
20070605-11:26:56 (21497) failed to find slave socket - (RuntimeError)
20070605-11:26:56 (21497) /usr/local/lib/ruby/gems/1.8/gems/
slave-1.2.1/lib/slave.rb:435:in `initialize''
2007 Mar 13
3
Scheduled worker dies after about 30-45 runs
I have a scheduled worker that runs every minute, checking for new eBay
auctions to post. If it finds an auction, then it posts it. If there are no
auctions in the database that are queued up, it simply does nothing. I got
the worker to finally run as a scheduled worker, every minute. However,
after about 30-45 scheduled runs, it simply stops running.
My backgroundrb_schedules.yml file:
------
2007 Mar 13
5
worker starting twice
Hi gang,
Thanks to other help I''ve gotten on this list, I''ve got backgroundrb
up and running using postgres alongside my rails app. I''ve designed
the system to have several eternally-running workers that periodically
poll the database to see if there''s any work for them to do, and set
things up in the config file to make them restart quickly if any of
them
2007 Mar 29
3
thread pool
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