Actually the entire premise of Steve's book is that he was in charge of performance/latency at Yahoo, and started out looking for issues in the backend.
But when he measured end-user latency, he realized that all the issues were in the front end. It doesn't make sense to start tweaking 100,000 lines of C++ code to shave 1 ms from the backend response time when you're taking 200-300ms to load JavaScript and such.
I think this is probably a common performance characteristic at large companies; perhaps not small ones. At small ones you probably have a database bottleneck. But at companies Yahoo/Google the backend engineers have generally optimized things quite a lot (partly because that kind of work is rewarded), and there's a lot of flab in the front end.
Comments
Actually the entire premise of Steve's book is that he was in charge of performance/latency at Yahoo, and started out looking for issues in the backend.
But when he measured end-user latency, he realized that all the issues were in the front end. It doesn't make sense to start tweaking 100,000 lines of C++ code to shave 1 ms from the backend response time when you're taking 200-300ms to load JavaScript and such.
I think this is probably a common performance characteristic at large companies; perhaps not small ones. At small ones you probably have a database bottleneck. But at companies Yahoo/Google the backend engineers have generally optimized things quite a lot (partly because that kind of work is rewarded), and there's a lot of flab in the front end.