Hi,
I wanted to share my current approach for autoscaling heroku workers, which
seems to be working well for me. Here is the
gisthttp://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
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.
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,
Hey Pedro,
As someone who's still learning uh, Heroku, Rails, Git, Delayed
Job . . . how do I go about using this?
At the moment I'm using collectiveidea's branch of delayed job, with
changes of my own to support Log4r. Should I switch to using your
fork of Delayed Job in order to access the
Roman,
Did you try Pedro's suggestion above(autoscaling)?
On Wed, Jun 23, 2010 at 9:55 PM, Roman Catz trusc...@gmail.com wrote:
In addition, could anyone provide good solution for running short
tasks from time to time but in preset time, I do not now time exactly
because user define it by
Pedro,
This is great!
One concept I got from a 2007 IT Conversation podcast interviewing GigaVox and
SmugMug:
You are optimizing cost vs responsiveness.
Reducing the granularity of startup and shutting down of instances saves quite
a deal of money.
Don MacAskill spoke more about this and
In addition, could anyone provide good solution for running short
tasks from time to time but in preset time, I do not now time exactly
because user define it by itself. Running full worker will be
expensive for this type of project.
--
You received this message because you are subscribed to the
Hi Chris,
There is. I made a little proof using DJ that might give you some insight.
The code is on this branch:
http://github.com/pedro/delayed_job/commits/autoscaling
And instructions/notes are on the comments here:
Hi guys: I saw an old thread on this but there seemed to be no answer.
Is there a way within my app to shut down and restart all the workers
programmatically? I have a twitter harvesting app which requires it
and I need to do it manually. Is there a doc somewhere which
describes how to do it?
