Every now and then when we see this, we simply 'heroku ps:restart' a few times so your dyno moves out of one EC2 instance into another. I've seen situations where one of the dynos (we have multiple too) is slow while the others are okay. Restarting them seems to fix this problem. YMMV.
K. --- http://blitz.io @k0ws1k On Mon, Feb 13, 2012 at 7:39 PM, WilliamF <[email protected]> wrote: > Hi all, > > I'm struggling with an issue where every request, with 0 load, takes 2+ > seconds. > > Environment: > > 4 dynos > 0 traffic (watching the heroku logging live) > controller simply has 1 line in it: render :text => "pong" > Subsequent requests route over the dynos, so the Heroku routing seems to be > working > The times average 8-12ms for the request, but 1600-2200ms for the "service" > > > Heroku has asked me to use NewRelic to troubleshoot this. But, here's the > deal, NewRelic doesn't show any delay..they show the request times, not the > service times. > > If anyone has any thoughts I'm all ears, thanks! > > W > > > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/heroku/-/hKxPVEaZFJMJ. > 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.
