To reproduce just go to any non-cached profile. If I open the forum on a browser which does not usually access it and click on a random profile, it will take a long time to load the summary.json file.
5 Likes
Has been an issue since the Discourse version upgrade. Thanks for reporting
3 Likes
Hi, thanks for reporting this. Our team will investigate this and will get back to you once we have an update.
3 Likes
Sorry for the late reply. Though we don’t have an answer, the summary.json of Discourse is a computed resource depending on when it was last accessed.
There’s a similar bug reported on Discourse Meta here
Note that for my testing, I noticed that disabling the browser cache doesn’t affect performance nearly as much as hitting a cold user.
I don’t have a solution now, but we’ll continue to look and see what we can do to optimize the summary.json query or have a reasonable caching solution in place.
2 Likes

