Forum: Ruby on Rails background jobs , comparison esp for sending emails

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
C25d913c4111f0db9ca31f0595eba878?d=identicon&s=25 Tom Tom (tingle)
on 2010-12-10 22:10
(Received via mailing list)
hi, im new to backgroundjobs etc. a quick look revealed a lot of
is there any kind of comparsion out there? im looking into this coz i
have a
lot 'notification emails' triggered by observers which i kinda want to
exclude from the workflow and pass it on into a 'mail' queue or similar.

any ideas if there is a comparison etc out there?

2c036193344d9e20914ed4968d0b3656?d=identicon&s=25 tramuntanal (Guest)
on 2010-12-12 14:51
(Received via mailing list)
You can follow engine yard recomendations:
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
and use raw crons because the background server failed a lot.


2010/12/10 tom <>

>  --
> 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
> To unsubscribe from this group, send email to
> .
> For more options, visit this group at

91a72b0ad3e43e3ef3a31816667ec694?d=identicon&s=25 Bill Walton (Guest)
on 2010-12-12 14:59
(Received via mailing list)
I'm using Background Job to send emails with the same objective.  It's
working well.,

Fce8e97a4f558dcdd7d6a64f02c493a6?d=identicon&s=25 Vladimir Rybas (Guest)
on 2010-12-12 18:13
(Received via mailing list)
I usually use Delayed Job, but it seems like not a best solution for
highload apps. Here is nice article about Resque
but haven't tried it yet.
00973881979aa0a660ffbbb2f7a907fb?d=identicon&s=25 Peter De Berdt (Guest)
on 2010-12-13 09:06
(Received via mailing list)
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.
This topic is locked and can not be replied to.