Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:litemage:customization:keeping-public-cache-warm-indefinitely [2016/04/27 18:09]
Rob Holda
+++ litespeed_wiki:cache:litemage:customization:keeping-public-cache-warm-indefinitely [2016/05/11 14:47]
Rob Holda removed
@@ Line 19: / Line 19: @@
 **Note:** This can be done on a per-store basis by changing your Current Configuration Scope.
-**Note:** It is possible that LiteMage will not finish crawling your site within the set **[[litespeed_wiki:cache:litemage:configuration:cache_warm_up#maximum_run_time_seconds|Max Run Time]]**. This can be caused by a large site or a high server load at run time, where the crawler will stop to prevent it from using up your remaining server resources. In these cases, the crawler should continue where it left off on its next run. This may cause parts of your site to not remain in cache. You can restart a crawlers queue without flushing your cache by clicking the reset link at the bottom of the **System→Cache Management** page in the Magento Admin Panel.
+**Note:** LiteMage will not crawl your site all at once. In order to prevent the crawler from using all of your server's resources and allow flexibility, the crawler will be run once every 10 minutes (600 seconds). You can set the **[[litespeed_wiki:cache:litemage:configuration:cache_warm_up#maximum_run_time_seconds|Maximum Run Time]]** for a crawler run to any value less than 600 seconds, the default duration being 5 minutes (300 seconds). When the crawler reaches this time limit, it stops until it's next run and then resumes where it left off. If your **Default Public Cache TTL** setting is too low, parts of your site will not remain in cache.
+**Note:** You can restart a crawlers queue without flushing your cache by clicking the reset link at the bottom of the **System→Cache Management** page in the Magento Admin Panel.
 **Note:** Users can also set their own **[[litespeed_wiki:cache:litemage:configuration:cache_warm_up#custom_defined_url_list|Custom Defined Url list]]** in case they wish to refresh certain URLs more or less frequently than their crawler queues.
-**Note:** Refreshing the cache is **[[litespeed_wiki:cache:litemage:administration#litemage_crawler_warm-up_status|not the same]]** as invalidating it.
+**Note:** If, after updating a page, a user wants to refresh the cached copy of this page, they can use the following command in a cron job to refresh the cached copy programmatically: <code>curl -A "litemage_walker" https://your_url</code>
+Refreshing the cache is not the same as invalidating it. When the cached copy is invalidated, the next user to hit the invalidated page will have to wait longer for the page to load as there is no copy to serve from cache. When the cache is refreshed, the cached copy is overwritten with the current version of the page.
+The difference between the [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:litemage:administration#all_administrative_privilege_browser_commands|LiteMage Purge command]] and the curl command listed above is that the Purge command invalidates the cache for the current page, while the curl command refreshes the cached copy of the given URL.