3 ms·
There are some interesting points here on how Heroku internals can affect your app: > An important outcome of these tests is that the slow-response situation i
by pritambarhate 10y ago
There are some interesting points here on how Heroku internals can affect your app:
> An important outcome of these tests is that the slow-response situation is outside of your control unless you’re running single-tenant (performance) dynos.
- lossolo 10y agoIt's like almost every "cloud" works. This are just VMs with a lot of noise from your neighbors. That's why i always use bare metal. Control over whole CPU and cache lines can be game changer if you have cpu intensive applications.
- Rapzid 10y agoMost AWS instances over a certain size have pinned cores and you'll see very little steal time unless something is up. That said, something might be up! I've seen it and the big players(netflix) monitor for this and re-prov accordingly.
- jon-wood 10y agoYou may have pinned CPU cores, but there's still contention for other resources such as disk IO and network unless you've got dedicated interfaces for them as well, and that's just within your own instance - downstream you've got shared routers, and the various AWS services you're probably depending on as well.
- dansingerman 10y agoIt's more then just that with heroku's random routing. If you are on shared tenancy dynos, and your current configuration is nearing maximum capacity, then adding dynos can reduce performance. Not per dyno, but across the entire platform. Counter-intuitive but true.