3 ms·
Investigating this approach now. It won't fix the problem, but will certainly reduce the occurrence of blocked dynos. Thx! EDIT: will need to look into our mem
by toast76 14y ago
Investigating this approach now. It won't fix the problem, but will certainly reduce the occurrence of blocked dynos. Thx!
EDIT: will need to look into our memory perf though, looks like we'll need to do some work to get more than a couple of workers.
- joeya 14y agoI can confirm this. We experimented with Unicorn as a way to get some of the benefits of availability-based routing despite Heroku's random routing. Our medium-sized app (occupying ~230 MB on boot) would quickly exceed Heroku's 512 MB memory limit when forking just 2 unicorn workers, so we had to revert to thin and a greater number of dynos.