4 ms·
Definitely a timeout unfortunately. We're bumping up dynos, so hopefully it'll get better!
by timtamboy63 12y ago
Definitely a timeout unfortunately. We're bumping up dynos, so hopefully it'll get better!
- deleted 12y ago[deleted]
- codelitt 12y agoI'm getting timeout errors too. Rather than just "more dynos," on Heroku - you may want to try: - Adding caching static assets/images/etc (Not sure how this is done on Heroku but fairly straight forward with Nginx or Apache). Currently, your assets are taking a full 6 seconds to serve. - Possibly serving your static homepage etc from one server/Heroku instance and your functional app from another so you don't put the stress of traffic on a homepage on the app server as well. Edit: Adding this link to be a bit more helpful. https://devcenter.heroku.com/articles/http-caching-ruby-rails https://devcenter.heroku.com/articles/http-caching-ruby-rail...