The maintainer of Resque (Terence Lee (http://twitter.com/hone02)) works for
Heroku. Failed Resque jobs can be retried via the built in web interface. I've
never had a bad experience with Delayed Job, but if you are using it heavily it
can impact your database performance.
--
Richard
Hi Carson,
You may also want to look at https://github.com/ryandotsmith/queue_classic
Ryan is also at Heroku. And designed this with the heroku infrastructure in
mind.
I have not used queue classic, but have had good experience with DJ and Resque.
(not a big fan of backgroundrb)
--Keenan
On
Richard Keenan,
Thanks for the feedback. This is going to involve lots of relatively small
jobs, and Resque looks like it might be a better option to get the db out
of the request cycle as much as possible.
For now I think I'll extract the logic out into a logical work unit that's
both DJ
Hi,
I've got a bit of processing that is not time critical but that is mission
critical, and I'm considering running as a Delayed Job in order to minimize
request times. My experience with Delayed Jobs on bamboo was that there
were times when the queue just hung, and I had to delete the jobs
