3 ms·
Personally, I don't see this. If you spend the time making sure that your application spins up nice and fast then the only downtime is from when Heroku decommi
by neilmiddleton 15y ago
Personally, I don't see this. If you spend the time making sure that your application spins up nice and fast then the only downtime is from when Heroku decommissions the old version of your application and the new one starts up.
I'm generally only seeing a lag of a few seconds at most, and no lost requests. I would look at your code and see what improvements you may be able to make.
- ryanbrunner 15y agoIt really depends on your environment. If you're using Rails, it's almost certainly 100% dependent on how many gems you're using.
- railsjedi 15y agoMost deployment allows for the site spin up independently before switching the load balance to it to provide a seamless experience. Even a very simple Rails sample app will often take over a minute to spin up on heroku. I don't think it's smart to completely focus on server startup time when the real fix is available on most other deployment environments. That said, I still like Heroku and can deal with this for a while until they fix it :)