4 ms·
Heroku Workers are pro-rated to the second, just like Dyno's. So the second you shut it down, the timer stops ticking. The time it takes to boot a worker mostl
by meskyanichi 15y ago
Heroku Workers are pro-rated to the second, just like Dyno's. So the second you shut it down, the timer stops ticking.
The time it takes to boot a worker mostly depends on your ruby application. The heavier it is, the longer it takes to boot up. Heroku spawns them fast, I think instantly because they are spawned from a compiled slug which is generated each time you push your app to Heroku.
The HireFire checkup interval takes at most 60 seconds, and less if more resources are available on HireFire's servers.
- bengl3rt 15y agoAnd presumably if I ran the HireFire open source library I could check even more frequently..?
- meskyanichi 15y agoThe open source library checks immediately when job gets enqueued, but this is because it does a post-create API request to Heroku every time it does it. Problem is that doing an API on reqests is terribly slow, which is one of the reasons that led me to create a hosted service out of it. See the HireFireApp homepage's text for more information, or check out it's knowledge base.