• Resolved alchemistGM

    (@alchemistgm)


    I’m totally loving W3 Total Cache. What are good numbers to use to precache a site with 40,000 pages, (how many seconds between, and how many pages per batch? anyone with experience on this?)

    And since some of these pages change very rarely, is there a good place to set them to only expire once or twice a year (I have been seeing things expire within hours, yet our CDN has been set to expire pages in one year).

    Im not using W3TC for server load; it’s just to make a faster user experience. So ideally I want things to never expire unless I say so, but 1 year would be an acceptable time also.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter alchemistGM

    (@alchemistgm)

    Well I tried 10 seconds between batches and 20 files per batch. but nothing happened. Ist there a “go” command to make it begin priming the cache?

    Also still have not found out where to set cached pages to never expire, (or expire far into the future). I could set garbage collection to be very long between but GC might be triggered at other times than when scheduled.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    No there is no go button and precise values depend on your server and traffic patterns, I have no formula for you.

    Thread Starter alchemistGM

    (@alchemistgm)

    That’s okay, I was juat wondering if anyone using that feature had discovered real-world values that worked for them. From you, I am taking the defaults as my best probable guidance ??

    With supercache, things seemed to expire in an hour no matter what we set in settings, but with W3 Total cache I’m happy to report that nothing seems to be expiring prematurely, so I think we’re okay on that.

    Thanks; I’m loving it!

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    It’s going to vary based on your server’s capabilities. The best thing to do is set a very high expire time for page cache (on browser settings tab) and when priming the cache, try to increase the number that are processed in the batch to keep more pages caches. The problem is if you cache your entire site too deeply WP Cron won’t run unless you’re using WP Admin heavily.

    Thread Starter alchemistGM

    (@alchemistgm)

    Good info, thanks. Good to know about WP Cron potentially getting crowded out also.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: W3 Total Cache] cacheing and preventing uncacheing’ is closed to new replies.