I have a small app which I have been using a Rake task for to execute a weekly database churn task which then mails out to bunches of users to update. I'm in the process of rolling this app out to a much wider audience and assuming that rake running on heroku means that it is running this on one dyno when the rake task runs and tying up that process completely (and I'm assuming rake just uses one dyno even if I'm using, say... 8 in the app.).
I do use this rake to weekly emails technique a lot in apps on normal machines but just wondering if there is a best practice for handling this in heroku, particularly where the processing job and email send out would be quite large. (I figure the better way to handle this is to rewrite the rake function so it dumps the processing to a /lib function and then dump the processing and email to delayed_job in order to make this inherently more scalable on heroku (and have workers pound it so it goes quickly without affecting the responsiveness of the application itself).) Any help or insight appreciated on what other people are doing with larger apps. thanks, Daryl. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. 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.
