• Hi,

    First of all, thanks for this great plugin!
    I am trying to understand the website cache expiration behaviour when Asset CleanUp is combined with W3 Total Cache (which I already had before installing Asset CleanUp).

    I have W3TC combining and minifying JS & CSS automatically, works fine.
    I have set Asset CleanUp to just combine the remaining JS & CSS. Which also seems to be working fine in this combination.

    I have however noticed some strange things happening wit the cache expiration. Originally I had W3TC set with long cache expiration for those files. With Asset CleanUp active however, it seems like the caching is cleared around every 8 hours? This of course results in a (temporary) slowdown of the website, as the browser needs to download the generated assets again before being able to take them from the cache.

    From what I understood so far, the expiration in W3TC and Asset CleanUp (for JS & CSS) need to be set to equal values, so I have opted to set them both to 14 days (= 1209600 seconds).
    > Asset CleanUp > Clear previously cached CSS/JS files older than 14 days
    > W3 Total Cache > Minify > Advanced:
    Update external files every: 86400 seconds (24 hours)
    Garbage collection interval: 86400 seconds (24 hours)
    > W3 Total Cache > Browser Cache > CSS & JS > Expires header lifetime: 1209600 seconds (14 days)
    >W3 Total Cache > Browser Cache > HTML & XML > Expires header lifetime: 1209600 seconds (14 days)

    My questions:
    1. will these settings really prevent the cache clearing of both plugins to NOT interfere with each other?
    2. Will clearing (purging) the cache in W3TC also clear the Asset CleanUp cache and vice versa?
    3. How can I assure both caches are kept in sync and cleared in sync?

    Thank you in advance for your help,

    Rob

Viewing 1 replies (of 1 total)
  • Thread Starter Rob de Cleen

    (@rdc2701)

    Additional related question:

    Your own docs state:
    When is the cache re-built and the optimized cached files updated?
    The caching expires in 8 hours and the optimized file is re-built after this time passes OR whenever the versioning for that file (the “/?ver=” value) is updated, whichever happens first.
    (https://www.assetcleanup.com/docs/how-css-js-are-created-within-the-caching-directory/)

    Why the fixed 8 hours expiry?
    And how may I change that to 14 days (provided there can be manual purging when needed).
    Should it not be enough to clear the cache ONLY when the versioning for that file changes?

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Questions about Asset CleanUp with W3 Total Cache’ is closed to new replies.