Update and apologies:
It’s now clear to me that (as might be expected!) qc-c cache files are not being created after disabling Quick Cache Pro – that was a mistake on my part – and I apologise to the developer for any confusion.
I am still experimenting with QC settings to minimise the build-up of cache files, since they are clearly tipping me over my memory allowance. But they may not be the only cause.
To be fair to the developer, there could be a memory over-use elsewhere in my WordPress installation (small as it is), but the only thing I can control, for the moment, is the size of the cache.
As I said earlier; disabling all plugins did not fix the memory problem, so if anyone could offer suggestions for investigating excessive memory use in a WordPress installation, it would be greatly appreciated.
Thank you.
@rubendasilva Thank you for the detailed report. I’m sorry that you’re having trouble, but you’re right that it does sound like it might be something else related to WordPress (or even something else on your server) causing the memory issues. I haven’t heard of Quick Cache causing memory issues like that, and there have been tens of thousands of installs.
That said, I’m certainly not ruling it out as a possibility. Regarding the large number of cache files: I’m aware that QC can potentially create a large number of files and I’ll be working on a feature to give QC a branched cache structure (see Issue #3 on GitHub).
If you haven’t already, you might want to try installing the WP Memory Usage plugin to see if that helps you monitor things. Also, see section of the WordPress Codex on Increasing memory allocated to PHP.
Thanks Raam Dev . . I will look into your suggestions.
All best
Ruben
From my personal experience with a huge website, if your siteurl has www and you request the non-www page, you may get that error (and vice-versa with the www).
The solution was to use a redirect before reaching wordpress: http://stackoverflow.com/search?q=htaccess+redirect+www.
