If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value. If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds. There’s no right or wrong settings for garbage collection. You can be informed on garbage collection job progress. Setup how often garbage collection should be done.ģ. After this time they are stale and can be deleted.Ģ. How long cache files are considered fresh for. On the advanced settings page you can specify:ġ. Garbage collection happens on a regular basis and deletes old files in the cache directory. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Your cache directory fills up over time, which takes up space on your server. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.
This is done by enabling “Preload Mode” in the settings. To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. You can generate cached files for the posts, categories and tags of your site by preloading. If you need more information than the following, you can have a look at the Developer documentation.
Translation of the plugin into different languages is on the translation page. Active development of this plugin is handled on GitHub. Afterwards a garbage collection of all old files is performed to clean out stale cache files.Įven with preload mode enabled cached files will still be deleted when posts are modified or comments made. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. Garbage collection of old cached files will be disabled. Preload as many posts as you can and enable “Preload Mode”. There’s no correct value for the expiry time but a good starting point is 1800 seconds.Ĭonsider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you. Garbage collection is the act of cleaning up cache files that are out of date and stale. If you’re not comfortable with editing PHP files then use simple mode. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. You can have dynamic parts to your page in this mode too. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. It’s the most flexible caching method and slightly slower. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. This is mainly used to cache pages for known users, URLs with parameters and feeds. You can keep portions of your page dynamic in this caching mode. htaccess file doesn’t need to be changed. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. Supercached static files can be served by PHP and this is the recommended way of using the plugin. htaccess file which is risky and may take down your site if modified incorrectly. This does require the Apache mod_rewrite module (which is probably installed if you have custom s) and a modification of your. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This completely bypasses PHP and is extremely quick. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. The plugin serves cached files in 3 ways (ranked by speed): If they are logged in, or have left comments those details will be displayed and cached for them. Other visitors will be served custom cached files tailored to their visit. One cached file can be served thousands of times. SUPERSPEED SUPERCACHE PASSWORD
Or users who have not viewed a password protected post.ĩ9% of your visitors will be served static html files. Users who have not left a comment on your blog. The static html files will be served to the vast majority of your users: After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts. This plugin generates static html files from your dynamic WordPress blog.
0 kommentar(er)
