3 ms·
On the other hand, the StackExchange workflow allows for very aggressive content caching - they probably wouldn't be able to maintain the same performances if t
by andrea_s 12y ago
On the other hand, the StackExchange workflow allows for very aggressive content caching - they probably wouldn't be able to maintain the same performances if they needed to generate content on a finer level.
edit: a few additional details - from a few years ago, alas http://highscalability.com/blog/2011/3/3/stack-overflow-architecture-update-now-at-95-million-page-vi.html http://highscalability.com/blog/2011/3/3/stack-overflow-arch...
- y0ghur7_xxx 12y agoThat DB does 343M queries/day. If the average page requires 10 queries to render, that's 397 pages/second the db would be able to return data for. This math is obviously an average, but even if you halve that number you are still very much above everything most of us web devs are ever going to build or even see.
- andrea_s 12y agoAbsolutely! I was not demeaning their expertise, just saying that their workflow is helpful in reaching such impressive performances with seemingly so little hardware...
- JanezStupar 12y agoWell as soon as you start fiddling with performance one of the first things you figure out that to eliminate the worst bottlenecks you need to simplify the workflow around them.