After six days there are now 2136 cache files. That seems a bit excessive given the limited number of pages and posts on the site.
Is there something that’s causing duplicate cache files to be created?
@otheroom If you have a lot of tags or categories, also consider all the possible variations of those pages that might be cached. For example, there might be an archive page for each tag (example.com/tag/mytag/) and one for each category (example.com/category/mycategory/). Then you’ll have the paginated pages (example.com/tag/mytag/page1/, etc.).
I suggest looking at your web server access log to see what URLs are being visited. You might have a web spider or search bot that is indexing your site, following all possible links it finds and thereby generating all the cache files.
If you discover this is what’s happening, you may want to look into excluding the offending bot using a robots.txt file. You can also exclude certain WordPress theme files from being cached altogether (such as the category or tag archives). See here for more information: https://github.com/WebSharks/Quick-Cache/issues/57#issuecomment-31583251
Could there be a hard disk or number of cache files limit introduced?
I’m facing a similar problem and the cache directory grows indefinitely until the host hd allocation is reached whereafter the site breaks.
@kalligator I’m working on a feature called Branched Cache Structure that will change the way cache files are stored on disk. Please follow this GitHub issue for more details: https://github.com/WebSharks/Quick-Cache/issues/3
Hello,
The latest version of Quick Cache (v140605) introduces a new Branched Cache Structure, in which cache files are stored in subdirectories that match the URL:
New Feature: Branched Cache Structure. Cache files are now written to the cache directory using a more intuitive format of PROTOCOL
/HOSTNAME
/PERMALINK
(e.g., http/example-com/sample-page.html
). For more details, please see https://github.com/WebSharks/Quick-Cache/wiki/Branched-Cache-Structure
See also: v140605 changelog.