Large Cache – Short Lifespan

Hello,

How many pages and posts do you have?
Do you have a link to the webpage (frontend)?

32 pages
177 posts
5157 listings (it’s a business directory site)

Do you have a link to the webpage (frontend)? – Are you asking for the site URL?

Yes I meant the site URL. But looking at your numbers, the cache size looks normal for the amount of posts. The number of files should reach 5157 + 177 + 32 + archives, and double that if you selected to create a separate mobile version.

The preloader will go through all you public posts or sitemap and generate the cache file.

• This reply was modified 5 years, 6 months ago by Marc Lacroix.

https://www.localbizus.com

So should I
1) reduce the number of files
2) shorten the lifespan to less than 3 hours
3) change the pages that are cached

I guess I had some confusion that the growing cache was related to activity by crawlers. It’s likely not actual searches by a person. My maps API was hijacked recently and while it’s now restricted I am still wary.

Multiple times a day I receive notifications that my security plugin (Wordfence) has blocked login attempts and crawlers.

Thanks for the help with this

I just visited your site, and when clicking on a link, I was blocked by Wordfence, saying I “Exceeded the maximum global requests per minute for crawlers or humans.”. I only went on the homepage, so maybe some settings are a bit too strong?

If your disk space is enough, I wouldn’t worry about the size it takes, as it will stop once all the pages are cached.

In the “Preload” tab, did you press the “Run now” button, or activated the “Schedule preloader”? This would crawl through all your pages and posts to create the cache files.

The lifespan value should depend on how often your content is updated. Some actions will renew the cache for certain pages. For example updating a post will clear its cache, as well as when a comment is approved. Reducing it too much will void the purpose of caching, so I wouldn’t set it much lower.

I really appreciate your insights on this.
I have changed some of the lockout settings to be less restrictive.
I scheduled the preloader to be the same as the cache lifespan and increased lifespan to 12 hours from 3.

Also if you find that the preloading uses too much of your server’s resources (because you have many pages), you can turn it off. When a user will visit a page, it will automatically check if the cache has expired, and regenerate that page if needed.

The preloader only ensures that all pages are always cached.