Timeline for Comment Table Size Results in Slow Page Loads and 500 Errors
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23 at 12:31 | comment | added | Mark Kaplun | DB server on the other side of the world from the app server? sounds like a good reason to leave the hosting company just for having people that can imagine this kind of setting (at least until light speed will be proven to not be constant). But on the useful side, if you have 80 queries it means your caching sucks... don't think there is any plugin to optimize this but typically you can cache all comments already displayed once (as they do not change) and fetch only newer comments. As comment table has the post ID as an index I find it hard to believe the issue is specific to comment but... | |
| Jun 8, 2022 at 5:40 | vote | accept | Rick Hellewell | ||
| Jun 7, 2022 at 21:50 | history | answered | Rick Hellewell | CC BY-SA 4.0 |