Tom, You can start with the new relic add on, and watch response times, and queue depth.
What I've done in the past is run some load tests through a local deployment to get a sense of how many requests the app can handle on a 'similar' stack (postgres, thin, etc). Then I run the same load tests against the app deployed on heroku, while monitoring with new relic, to see if the times are close, and where the time is being spent. Based on that you get a rough idea of how many requests a single dyno can handle for your app, and what you might need to do if you are expecting a significant uptick in requests. Before you look to purchase more dynos, see if you can leverage the browser cache more effectively, and then look for what can be put in the varnish cache. You want to make sure that you aren't wasting your dyno by having it serve up requests for static assets like css, js, images, etc. Then you want to use page caching if you have places where that will work. Good luck! -John On Fri, Mar 18, 2011 at 7:56 PM, Tom O'Neill <[email protected]> wrote: > Hey guys - > > What's the best way to monitor my site's serving capacity/performance? > E.g. how can I tell when it's time to buy more dynos? > > Thanks! > Tom > > -- > 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. > > -- -John -- 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.
