1. you need to set a cronjob. I added a explanation for the note. you can check it.
https://www.wpfastestcache.com/features/restart-preload-after-completed/
2. if you don’t select that option, the preload feature will not restart until the entire cache is deleted.
You can set as */2 (every two minutes)
Thread Starter
chcw
(@chcw)
@emrevona
In https://www.wpfastestcache.com/features/restart-preload-after-completed/ , you said “In this case, instead of clearing the entire cache, generating the entire cache in time ensures much less CPU usage.”, then what is the difference between clearing cache and generating cache. I think re-generating cache will first clear cache and the generate cache, so there are no difference between them at all.
If set “Clear Cache” for new post and updated post, then is it still necessary to use preload feature? As Clear cache will also regenerate cache for new post and updated post already.
If processing 4 pages per post, then for 2 minutes, only 8 pages will be cached. If we set cron job to restart the preload, then there will be the case that the pages in the previous preload process are not processed completed, while a new preload process is started, overlapped with the previous one. WIll that cause problems?
what is the difference between clearing cache and generating cache. I think re-generating cache will first clear cache and the generate cache, so there are no difference between them at all.
Thanks to you I have the opportunity to improve the tutorial. Please take a look at the new changes on the following turorial.
https://www.wpfastestcache.com/features/restart-preload-after-completed/
If processing 4 pages per post, then for 2 minutes, only 8 pages will be cached. If we set cron job to restart the preload, then there will be the case that the pages in the previous preload process are not processed completed, while a new preload process is started, overlapped with the previous one. WIll that cause problems?
You can increase the number on the preload wizard.
Thread Starter
chcw
(@chcw)
@emrevona
Thank you.
You can increase the number on the preload wizard.
If I have 3000 pages, and the cron job is set the start every 2 minutes, then does that mean I need to set 1500 pages per minutes so that all pages can be processed before a new process is started?
why do you need to re-generate all the cache in 2 minutes? you can set the number as 15 and you can set the cronjob “every minute”. 15*60=900 pages are cached in 1 hour. After 3,5 hours all cache are generated again.
but if you have a dedicated server, you can set the number as 50-60 surely.
Thread Starter
chcw
(@chcw)
@emrevona
Because you suggest to set the cron job to auto restart the re-generation of cache for every 2 minutes. If set number to 15, then after 2 minutes, only 30 pages are cached and remaining 2970 pages are still in processing. Then the next re-generation process is started by the cron job. So in my first post, I just ask if a new cache generation process will conflict with an old cache generation process? Will both processes try to generate cache for the same page twice? Or will that cause share violation?
Thanks
So in my first post, I just ask if a new cache generation process will conflict with an old cache generation process? Will both processes try to generate cache for the same page twice? Or will that cause share violation?
there is no two cache generation process. Cronjob and native preload processes are not separate processes.
