We are using Nanite, amongst other things to generate complex mails
and send them off. Works brilliantly and we don't even load the Rails
environment into the nanite workers, making every worker a nicely
contained, very memory-friendly entity. Nanite is very scalable.
On 12 Dec 2010, at 18:11, Vladimir Rybas wrote:
I usually use Delayed Job, but it seems like not a best solution for
highload apps. Here is nice article about Resque
http://rubylearning.com/blog/2010/11/08/do-you-know-resque/
but haven't tried it yet.
On Sun, Dec 12, 2010 at 4:57 PM, Bill Walton <bwalton...@gmail.com>
wrote:
I'm using Background Job to send emails with the same objective.
It's
working well.,
HTH,
Bill
On Sun, Dec 12, 2010 at 8:50 AM, tramuntanal
<tramunta...@gmail.com> wrote:
You can follow engine yard
recomendations: http://www.engineyard.com/products/technology/stack
explore: http://github.com/ezmobius/nanite
or use raw cron
I advice that EngineYard recomendation against backgroundrb is
realy true. I
had to remove backgroundrb from a production app (not hosted in
EngineYard)
and use raw crons because the background server failed a lot.
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
