by admin » Wed Apr 28, 2021 11:27 am
hello, instead of using cache pls consider fixing the issue that causes the slowdown.
generally cache is very dangerous in matters of any XSS that can occur on your site - core Joomla and sometimes core VM in every 5th to 10th version include an XSS vulnerability which might get stored at your cache and thus cause a huge security problem.
general optimalization should include:
- checking for any remote calls from any extensions (as this one is the slowest part usually)
- checking for the database indexes and queries that take most of the time
- check for ineffecient code such as infinite loops or php based url cron taks (awo + fsf + etc... )
to further investigate which modules and plugins cause the slowdown you can install our "benchmark plugin" + enable global joomla debug + disable system-debug plugin and see the output of the variables within the JS console of g.chrome. the benchmark plugin must not be run on a production site (as it reveals too much data and might not use very up-to-date overrides per latest joomla version )
usually on our hetzner based servers with m.2's SSDs and ramdisks for session and some cache handling we usually are much better off (faster) when using our "nocache" system (which prevents any cache writes) compared to using any sort of cache that uses file storage.
best regards, stan