a W3C action is eating alot of CPU

@vmarko Hello, so i turn off the cron now.
I am sure now that the cron is not triggering anything.

but this strange behavior didn’t stop, as like as someone is visiting all pages

please take a look at this disk monitoring screen
https://paste.pics/5268dd124563ec36a1941f80dcd405a1

it has a stable pattern of getting low in space. (I think The w3c-plugin wipe the cache automatically when it reach to some point)

(i send you the page cache screens above this message)

Hello @tavakal4devs

Thank you for the screenshots and thank you for the feedback.
I can see that W3TC Preload is not enabled and there is nothing to suggest that any option in the W3 Total cache is causing this.
With the settings you currently have enabled (Only Page Caching), the pages should be cashed on a visit. Since the W3TC Preload feature is not enabled, and the sitemap is not added to the designated field (W3TC needs to use the sitemap to crawl and cache all pages), it means that W3TC is only responsible for caching the pages on a visit.
One thing that I can confirm is that the website is very fast and yes all pages appear to be cached and each page has a different time stamp within 4 hour period
Thanks!

@vmarko
So you confirm that this is NOT normal but the w3c is not responsible, and i should look somewhere else, correct?

Hello @tavakal4devs

I can confirm that W3TC is not doing this – caching all bases at once, so something other is causing this to happen and not W3TC.
Either some other plugin that may be crawling the pages for visits or your website traffic is huge.
Thanks!