3 ms·
I'm yet to see an update/fix on Heroku's recent PR nightmare on the random routing issue. Anyone?
by neya 14y ago
I'm yet to see an update/fix on Heroku's recent PR nightmare on the random routing issue. Anyone?
- coolsunglasses 14y agoI'm not sure why this point isn't being made, but they're not going to change anything about how the routing works, least of all for Bamboo. Heroku is past the point of caring about pushing the envelope, stateful routing is an infrastructure risk and overhead that primarily their least informed customers need or want. It's a high margin operation is a low margin business, they're trying not to fuck it up. So stop asking.
- neya 14y agoAs a customer, no matter what they do, whether it's a high margin risk or low margin profits, I'm supposed to be informed of their decision - whether they try to fix it or not, because I was one of the affected. They promised they would do so in their previous blog posts, hence the curiosity. >So stop asking. I have every right to ask and I will rightfully so. A disguised internet profile about sunglasses means nothing to me.
- joevandyk 14y agoThey are about to push an update that lets you run larger dynos, which reduces the risk of having all the requests to a dyno stuck doing something long-lived.
- redguava 14y agoI believe the larger dynos are mostly to better handle using Unicorn as the webserver. Unicorn allows multiple workers to run per dyno, and has it's own smart routing, so it compensates well for Heroku's routing system. The downside to Unicorn was that the workers share a dyno's memory and often you couldn't have more than 2 per dyno with 512mb memory. This change helps that a lot.
- dserodio 14y agoThey've put together a FAQ about routing: https://blog.heroku.com/archives/2013/4/2/routing_and_web_performance_on_heroku_a_faq https://blog.heroku.com/archives/2013/4/2/routing_and_web_pe...