On Mon, Apr 2, 2012 at 11:22 AM, Richard Schneeman <[email protected]> wrote: > I do you have rack cache on your app? I recommend setting that up and using > memcache for the meta store. Also setting your expire headers on static > assets to a far future date. That should help with timeouts especially with
No rack cache, but these solutions are just workarounds for the underlying problem, no? We do use redis as a write-through cache for our CouchDB cluster, but not for static assets. > static assets. You can also try using a CDN but that is quite a bit more > work for sinatra > https://devcenter.heroku.com/articles/error-codes#h12__request_timeout > > You can also consider increasing your dyno count. What web server are you > using? Using thin and definitely running more than a single dyno. Interesting thing is the entries around the H12 errors, the other dynos are responding in 10/20 ms. That's why I thought it was kinda strange. Some time ago when this happened, I restarted the processes and the problem went away. Maybe the underlying EC2 instance was having issues? K. --- http://blitz.io @k0ws1k -- 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.
