4 ms·
I have worked in a project which required double infrastructure of what SO is using and render page at > 200ms. Our db size was 1/4 of stackoverflow but we don'
by kburman 6y ago
I have worked in a project which required double infrastructure of what SO is using and render page at > 200ms.
Our db size was 1/4 of stackoverflow but we don't even have 0.1% of content was stackoverflow offers.
- GordonS 6y agoWhat stack were you using? The only time I've personally seen render times that high is with large, complex databases in bad need of indexes and/or restructuring, and with hybrid cloud stuff, where cloud services are using an on-prem API or database.
- f6v 6y agoDo live queries for frequently accessed data without caching and you can go into seconds to render a page. I once came across a Postgres full-text query without an index. The page took a minute to render, I kid you not. And that page was arguably crucial to internal operations.
- kburman 6y agoRails, but I won't say rails was any way responsible for all this. It was poor design choices from our side. It was a large database due to unnecessary complexity and we do have indexes but due to poor design it was hard to gain any significant performance gains from adding indexes.