It's not worth the effort probably, even if you could. Usually the bottle neck becomes the DB anyway.
Sent from my iPhone On Mar 19, 2011, at 2:13 AM, Ben H <[email protected]> wrote: > I am trying to work out how to respond to increasing/decreasing > traffic to my Heroku site with dynos management from within the app > itself. > > I know you can access HTTP_X_HEROKU_QUEUE_DEPTH or > HTTP_X_HEROKU_QUEUE_WAIT_TIME and use those to set the amount of > dynos. What I'm wondering is what process to use to do the checking. > > Is it okay to add an after_filter to every action in the app to do a > check against some threshold, and if a threshold has been met, change > the number of dynos? I would only have 5/6 thresholds, so for vast > majority of users the only impact would be the increased time it takes > to do the check, and then for a handful of users it would be the check > + the changing of dynos time. > > Would it be too much of an inconvenience to the users? Is there a > better way? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
