-
there are: you may reduce the modules that you use in the page and for the modules that show several results you may adjust them to get balanced results, for instance timeline to show 10 posts each time the page is scrolled or posts module to show 4-5 latest posts each time. these will lighten the query and computation load accordingly.But applying the notification settings trick will create the most effective result for page speed.
PS: my recommendations here are for getting the optimum result from the current UNA code base. To do changes to it is a discussion with the developers.
-
Tested small notifications number - Zero difference. Exactly the same, so thats not it.
The number of entries per page? Its already low. 12 per page.
This is an architectural problem that 100% needs developer input. The problem here is that I am operating at scale, with a pretty large data set. Even with reasonable settings, its still slow. I would also argue - if there WAS something wrong with the current settings, that the default "out of the box" values would need tuning to help new users. I have intentionally avoided changing very much to allow elimination of custom setup as a contributing factor
-
my system has 15K+ users. If your site is new yes notification setting will not effect that much but if it is a few years old with many pooled user activity it will create a big change. also mariadb and UNA 12.1
-
Comment to 'The need for speed'
Comment to The need for speed