On Thursday, 15 October 2015 at 09:24:52 UTC, Chris wrote:
Yep. This occurred to me too. Sorry Ola, but I think you don't know how sausages are made.
I most certainly do. I am both doing backend programming and we have a farm... :-)
Do you really think that all the websites out there are performance tuned by network programming specialists? You'd be surprised!
If they are to scale, then they have to pick algorithms and architectures that scale. This is commodity nowadays. You want to get as close to O(1) as possible for requests. This is how you build scalable systems. No point in having 1ms response time under low load and 10000ms response time when the incoming link is saturated.
You'd rather have 100ms response under low load and 120ms response time when saturated + 99.9999% availability/uptime.
Robustness and scaling costs latency, but you want acceptable and stable QoS, not brilliant QoS under low load and horrible QoS under high load.
Scalable websites aren't designed like sportcars, they are designed like trains.
