• Resolved Martin

    (@martyshka)


    Hello,

    I would like w3 total to keep a cached page valid for as long as possible (not considering manual cache flush). But the pages seem to be invalidated (“.old”) in a few hours. How can that be changed to a much longer (or indefinite) time?

    preload settings are:
    update inteval: 600
    pager per interval: 10

    Garbage collection interval: 7200

    As I understand garbage collection after reading your support pages, it has nothing to do with the time of validity itself: “The “Garbage Collection Interval” setting refers to the frequency at which expired cache data is removed from the cache storage. In the context of caching, garbage collection is the process of identifying and removing cache entries that have expired or are no longer valid.”

    What needs to be done to prevent the page from becoming invalid in the first place?

    Best regards
    Martin

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @martyshka

    Thank you for reaching out and I am happy to help!
    The .old pages are still valid untill deleted and those are there to serve the cached pages to the user until the new batch is cached

    You are using a couple of things. one of them is cache Preload which caches a batch of 10 pages every 60 seconds. Depending on the number of pages and the Garbage collection interval, this can overlap at some point.

    Is there a specific number of pages you are caching with the preload?

    Thanks!

    Thread Starter Martin

    (@martyshka)

    Hello @vmarko,

    thank you!

    I did not quite understand the question: “Is there a specific number of pages you are caching with the preload?” I would like to have most of the site (20 pages, 500 products, a number of product archives) available in the cache.

    I observed that pages cached as .old are not served from cache as fresh ones are when opened in the browser. They are compiled on that demand and only then simultaneously refreshed in the cache. Cached pages turn into .old in a matter of a few hours.

    Best regards

    Martin

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @martyshka

    Thank you for your feedback.
    So the cache preload runs in the specific period, in that period a specific number of pages are cached and when the cycle is reached the end of the sitemap, it starts from the begining.

    The update interval and the GC need to be compatible depending on the number of pages

    Can you please set Garbage collection interval to 2629800

    Let me know if this helps!

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Prolong time until cache expiration’ is closed to new replies.