Does Falcon have a garbage collection process?

Also, ask if Falcon will automatically create a cache in the background, in the same fashion as Super Cache actually does, or if pages with no hits will not have a cached version.

Hi Marcelo,
I suggest checking this list of events that cause Falcon cache to auto-clear. Knowing that, the cached version of any page isn’t created until this pages is visited.

Also you maybe interested in checking this script if you want to clear cache automatically on regular basis.

Thanks.

Hello, after reading a bit, I come with some questions:

If I publish/update any post/page/cpt, will its assigned categories and tag pages be cleared as well? This is an issue almost ALL cache plugins are failing to comply with (except for Comet Cache).

Also:

Whether or not you were logged in the cache will clear:
If a comment is posted the whole page cache is cleared.

So, the WHOLE page cache is cleared? or only the individual cached file for that page is cleared?

And last, but no least, will it work in the same fashion for all kind of Custom Post Types?

Thanks!

Hi Marcelo,
Regarding your first question, the answer is yes, I have just tested that on (post/custom post type) and the (tag/category) archives pages are not served from cache after I modified the (post/custom post type) title or content, so the cache will be deleted.

After posting a comment, the whole page cache is cleared, not only the individual cache file for that page.

Falcon cache should be working consistently with different custom post types, tested that with two different ones at my end here and it worked just fine.

Thanks.

After posting a comment, the whole page cache is cleared, not only the individual cache file for that page.

Why is that? After posting one comment, only THAT post should be cleared from cache. If I have a blog with 2500 posts, why in the world would be useful to clear the entire cache if one comment is made? It undoubtedly causes unwanted performance degradation. ?? Any thoughts on this?

That’s because some themes may include a “Recent comments” widget for example in the sidebar, so cache must be cleared to get these widgets working fine.

Please note that:

Wordfence does not clear your page cache as part of the current HTTP request when one of these events fires. Instead it ‘schedules’ a cache clear to run immediately, sends another HTTP request to your site and then returns data to your site visitor or logged in user. That way your user’s don’t have to wait for the cache clear to run before they get their response back from the server. Users are immediately sent a response and then the cache clear runs in the background as a separate request keeping your site responsive.

Also, one time visit to any of your pages is enough to generate the cached version of it, cached pages aren’t generated for all your pages at the same time, so it will not affect the performance to that extent.

Thanks.

Ok, but I don’t agree with the idea of clearing the whole page cache when ONE post is updated. You shouldn’t assume that any site may include or not a “Recent comments” feature because there are lots who don’t. Even on huge sites. So, this should be an option in the settings, left to every admin to choose if they want to clear all the page cache when ONE post is updated, or not. What do you think? Could this be a feature request after all?

I will make sure to discuss your suggestion with our dev team and add your vote for this feature.

Thanks.