-
Hello @Peter Fuchs !
Could you please specify - do you have any actual errors in your server's error log? And, of course, do you see any red warnings in the Studio->Dashboard->Server audit area?
-
Hello LeonidS,
Thank you very much for your quick response. There is currently no error message in the log file.
The server audit reports 'MySQL: thread_cache_size = 0 - FAIL (must be > 0)' and we still have to work on the two issues 'User-side caching for static content' and 'Server-side content compression'.
But I don't think that explains the initially long time for creating the cache files.
Is there perhaps a tool that can be used to warm the cache after deletion?
Best regards
-
There may be troubles with the fast write/read for the cache files on your server's hard drive. For a quick check, you may switch the cache engine from the Files to Memcache variant in the Studio->Settings->Cache are (if you have the ready Memache on your server).
-
We already use Memcache as a cache engine. Nearly all files of the 'cache' folder are stored there. However, this has no effect on the 'cache_public' folder. CSS, LESS and JS files are still stored in this folder.
-