• I recently ran into an issue of our site running out of memory during database backups. We use a plugin call Stream to track any admin task, and the source of our backup issue was the fact there was over 70,000 records in stream related to Comet Cache updating cache files.

    It seems to have repeatedly cached the home page, going through a sequence of page names
    wp-content/cache/comet-cache/cache/http/site-address/page/2257.html
    wp-content/cache/comet-cache/cache/http/site-address/page/2258.html
    wp-content/cache/comet-cache/cache/http/site-address/page/2259.html
    etc.

    Although checking via FTP, only one of these html files exists.

    Any ideas on what may be causing this?

Viewing 2 replies - 1 through 2 (of 2 total)
  • @nathan-adams Two questions:

    1) Are you using Comet Cache Pro with the Auto-Cache Engine enabled, or are you using Comet Cache Lite from here on www.remarpro.com (which doesn’t have the Auto-Cache Engine feature)?

    2) Do you have 404 Caching enabled? See Comet Cache → Plugin Options → 404 Requests

    Note that Comet Cache itself does not go through your site and cache things (unless you’re using the Auto-Cache Engine). The core mechanism that Comet Cache uses to ‘create’ a cache file is a request to your site. So when you visit a page on your site for the first time, if it has not been cached yet then Comet Cache will generate a cache file at that time. But unless and until a request to a page occurs, Comet Cache will not generate a cache file.

    The behavior you explained sounds like something is spidering your site and each of those requests is resulting in Comet Cache attempting to create a cache file. If those are non-existent pages, then Comet Cache will only attempt to create a cache file if 404 Requests caching is enabled.

    Thread Starter Nathan Adams

    (@nathan-adams)

    Hi Raam,

    Thanks for your response. I’m using the Lite version of the plugin, and 404 Caching is not on.

    I think you’re right about spidering, as I can see large numbers of cache files being updated with identical timestamps. I’m guessing it’s going through ?p=1, ?p=2 etc. and if the post id matches a post/page, that isn’t ignored by the cache.

    I’ll up my security settings to crack down on multiple 404 requests and see how that goes.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Exceptionally large number of caching updates’ is closed to new replies.