3 ms·
> 1) Consider not running the largest instance you need to handle your workload, but instead distributing it across smaller instances. This allows for progressi
by gravypod 7y ago
> 1) Consider not running the largest instance you need to handle your workload, but instead distributing it across smaller instances. This allows for progressive rollout to test new versions, reduces the thundering herd when you restart or replace an instance, etc.
I came here to say this. Horizontal compute is a miracle.
- verttii 7y agoDistribution itself might be a world of pain depending on the nature of your application. For example stateful apps where low latency is expected.
- semiotagonal 7y agoHow meaningful is the benchmark for handling idle connections? Handling more is better, of course, but if the server melts down when 0.1% of them have any activity, maybe maximizing idle connections isn't the right place to expend optimization effort?
- cortesoft 7y agoDepends on your workload
- sciurus 7y agoFor us, the experiment (https://blog.mozilla.org/services/2018/10/03/upcoming-push-shield-study/ https://blog.mozilla.org/services/2018/10/03/upcoming-push-s...) with mostly idle clients was very helpful, since it flushed out problems with out load balancing layer and in the end gave us confidence that it, our app, and our persistence layer could safely handle many more connections. If we had begun having problems once we started sending more push messages, we would have simply stopped using the new service (https://github.com/mozilla-services/megaphone https://github.com/mozilla-services/megaphone) responsible for that until we worked through them.