A busy website and cache timeout

  • ”Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site, you should set the expiry time to 600 seconds.”

    What does that exactly mean? Does that mean if the site is very busy, one should not use high cache timeout even if the content is static?

    I have 200-300 posts and 2k visitor daily. It’s all static content. So I should not use high cache timeout? Is that right?

Viewing 2 replies - 1 through 2 (of 2 total)

  • How often do you update your site? Do you get lots of comments? Do things change very often on your site? There’s no “right” answer to the question you ask but if you don’t have comments and don’t post anything I’d set the timeout to 86400, and have it check the cache every 3600 seconds.

    The former setting allows cache files to live for a long time (a day) while the latter setting means that the plugin will check for stale files every hour which might delete a handful of stale cache files. If you leave it longer it will have to delete more at once which can slow down your site.

    Thread Starter radorp2p

    (@radorp2p)

    I don’t update it much so I can set the cache timeout 1 day with no issues and I use wpdiscuz which seems not to be affected by wp super cache settings.

    I just wondered whether busy site/traffic is a factor for determining these values.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘A busy website and cache timeout’ is closed to new replies.