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 and Resque friendly, and then play around with both of them/get familiar w/ the internals and see how it goes. I'm still torn on whether the added complexity is worth it, or if I should just pitch the idea and simply pay for more workers if life gets busy. Thanks, Carson On Thursday, September 27, 2012 9:05:57 AM UTC-7, Keenan wrote: > > 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 Thursday, September 27, 2012 at 11:55 AM, Richard Schneeman wrote: > > 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 Schneeman > http://heroku.com > @schneems <http://twitter.com/schneems> > > On Wednesday, September 26, 2012 at 9:21 PM, Carson Gross wrote: > > 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 to get > things running again. I won't be able to just drop these jobs on the floor > like I could on our bamboo app, so I was wondering if anyone can comment on > the reliability of DJ's on the cedar stack, if they've had problems w/ > things hanging, etc. > > Thanks for any comments or opinions, > Carson > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+un...@googlegroups.com <javascript:> > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+un...@googlegroups.com <javascript:> > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
