Title: Preload cache
Last modified: October 15, 2020

---

# Preload cache

 *  Resolved [marcorroma](https://wordpress.org/support/users/marcorroma/)
 * (@marcorroma)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/)
 * Hi, when the preload cache is repeated, is the old cache previously generated
   cleared?

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

 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13544788)
 * you need to enable the “Restart After Completed” option.
    [https://www.wpfastestcache.com/features/restart-preload-after-completed/](https://www.wpfastestcache.com/features/restart-preload-after-completed/)
 *  [Jim](https://wordpress.org/support/users/jwmc/)
 * (@jwmc)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13549738)
 * The labeling and description of the preload options are confusing, at least to
   me. Here’s how I’m guessing it works. Please correct me where I’m wrong.
 * When you enable Preload, it starts creating cache files for all the checked post
   types, at the rate selected.
 * RESTART AFTER COMPLETED NOT SELECTED
    When it’s finished preloading, it checks
   every 5 minutes to see if the cache has been cleared. If so, preloading starts
   again.
 * WITH RESTART AFTER COMPLETED SELECTED
    I’m sorry, after reading the documentation
   on this option several times, I still don’t understand what it does.
    -  This reply was modified 5 years, 8 months ago by [Jim](https://wordpress.org/support/users/jwmc/).
    -  This reply was modified 5 years, 8 months ago by [Jim](https://wordpress.org/support/users/jwmc/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13554519)
 * > RESTART AFTER COMPLETED NOT SELECTED
 * When it’s finished preloading, the preload stops.
 * > WITH RESTART AFTER COMPLETED SELECTED
 * When it’s finished preloading, the preload starts again.
 *  [Jim](https://wordpress.org/support/users/jwmc/)
 * (@jwmc)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13554549)
 * So in the first case, if you clear the cache, preloading won’t start again? What
   does the 5 minutes refer to in
 * > The preload feature stars to work after delete cache.
   > When the Preload feature calls the urls, the cache of urls are created automatically.
   > When all the pages are cached, the preload stops working. When the cache is
   > clear, it starts working again.
   > The Preload runs every 5 minutes.
 * [https://www.wpfastestcache.com/features/preload-settings/](https://www.wpfastestcache.com/features/preload-settings/)
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13554553)
 * the preload starts after clearing cache automatically. it is not related to “
   restart” option.
 *  [Jim](https://wordpress.org/support/users/jwmc/)
 * (@jwmc)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13554565)
 * Thanks. Sorry to be a pest, but could you clarify what happens every 5 minutes,
   mentioned in the quote above. “Preload runs every 5 minutes”, sounds like the
   cache gets replaced every 5 minutes, but that’s not what happens.
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13554579)
 * The preload feature creates a cache every 5 minutes. if the “restart” option 
   is enabled, the preload feature creates cache and replaced with the old one.
 *  [gerryg001](https://wordpress.org/support/users/gerryg001/)
 * (@gerryg001)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13983421)
 * Just hitting the same questions. I think his answers mixed up the preload and
   restart aspects.
 * Jim, did you ever manage to figure this out?
 *  [Jim](https://wordpress.org/support/users/jwmc/)
 * (@jwmc)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13983447)
 * No, I could not really understand it or get it to behave as I expected. I switched
   to wp optimize. It is intuitive, well documented, and preloads completely and
   quickly.
 *  [gerryg001](https://wordpress.org/support/users/gerryg001/)
 * (@gerryg001)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13983478)
 * Thanks, Jim. I’ll give him one more try and see.
 * Do you recall if WP OPtimize will expire a cached url at the CDN when you do 
   a post update? It’s not clear from their description.
 *  [Jim](https://wordpress.org/support/users/jwmc/)
 * (@jwmc)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13983524)
 * Yes, it does.
    [https://getwpo.com/faqs/#When-does-WP-Optimize-clear-the-page-cache-](https://getwpo.com/faqs/#When-does-WP-Optimize-clear-the-page-cache-)

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

The topic ‘Preload cache’ is closed to new replies.

 * ![](https://ps.w.org/wp-fastest-cache/assets/icon-256x256.png?rev=2064586)
 * [WP Fastest Cache - WordPress Cache Plugin](https://wordpress.org/plugins/wp-fastest-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-fastest-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fastest-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fastest-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fastest-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fastest-cache/reviews/)

 * 11 replies
 * 4 participants
 * Last reply from: [Jim](https://wordpress.org/support/users/jwmc/)
 * Last activity: [5 years, 4 months ago](https://wordpress.org/support/topic/preload-cache-5/#post-13983524)
 * Status: resolved