<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I've used them both in a distributed fashion.<div><br></div><div>Resque - Worked better of the two when there were a hundred or so workers attached. My only problem with it is that it's not guaranteed to be durable. So if my Redis instance dies/restarts/whatever I need to be able to rebuild the queue. Easy enough done, just be mindful of it.</div><div>DJ - Meh. Ran into problems under heavy load. Ensuring failed jobs were removed and that there was proper indexing on the priority, run_at, etc. fields improved the situation. </div><div><br></div><div>I've been queue_classic for a number of months now without issue. It uses the NOTIFY event within postgres to hand work out to workers. For some reason I have more faith in something implemented at the DB level to work when I need it most.</div><div><br></div><div>G<br><div><br></div><div><br><div><div>On Jul 3, 2012, at 8:30 AM, Ed James (Alt) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
Hi all
</div><div><br></div><div>I've used both DJ and Resque before, so I'm familiar with both. However, I've never used them in a distributed architecture, where you have workers running on multiple machines. Resque seems to tout this as a feature a bit more then DJ, although the DJ docs say it is possible.</div><div><br></div><div>Has anyone had any experience in running either Resque or DJ in a distributed setup?</div><div><br></div><div>The primary reason for wanting to do this is for the ability to auto-scale (on AWS).</div><div><br></div><div>Thanks.</div>
<div><div><br></div><div>-- </div><div>Ed James</div><div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a></div><div><br></div></div>
_______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>http://lists.lrug.org/listinfo.cgi/chat-lrug.org<br></blockquote></div><br></div></div></body></html>