Hi, I wanted to share my current approach for autoscaling heroku workers, which seems to be working well for me. Here is the gist<http://gist.github.com/594782>, and here is a blog post <http://easymple.com/blog/archives/120> describing it in detail. Please note, this approach is different and definitely working better for me than the previous approach that I had shared. This approach is specifically applicable to the scenario where you want high availability for users relying on workers, and still not have to overprovision workers which may be idle.
Let me know how this works for you. Thanks Anand On Thu, Jul 29, 2010 at 12:45 AM, Anand Ramanathan <rcan...@gmail.com>wrote: > I havent had the need for multiple dynos, but this link seems to be about > scaling dynos, not workers - is that correct? > > > On Sat, Jul 17, 2010 at 10:58 PM, Ben Schwarz <ben.schw...@gmail.com>wrote: > >> I assume that you haven't seen this recent release from ddollar. >> >> http://github.com/ddollar/heroku-autoscale >> >> -- >> 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<heroku%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> >> > -- 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.
