Kind of funny, kind of sad, kind of infuriating. I spent about 6 hours figuring this out, and it ended up being the dumbest thing.
So I host this one site, it's getting about 3k users/day, not much. This site has these plugins WP Tabs and WP Show Posts and WP Popular Posts and Shortcoder. Well, the genius designer used all these plugins to make custom designed Pages to replace the regular category archives... The combo of plugins makes such a mess, the Tabs for example adds a bunch of long strings in the url bar, for the various tabs. Anyhoo, these pages don't seem to be cacheable, too many queries from the various plugins and the query in the url breaking cache. That's kind of important for what's next.
I checked the search console while investigating the irregularly high load generating seemingly from this site. In the page index area, there's some 10 million urls "crawled but not indexed", it's those weird urls from the tabs plugins lol...
So I check the access log... 50,000 get requests from Google today, all on those weird urls. Wow.
I added a rate limit on Googlebot to disallow more than 1 crawl per 5 seconds on those pages with those garbage plugins, and got instant results:
Load dropped from 11 to 2... Oh, and bandwidth dropped from 200Mbps to 30Mbps... I have no idea what Googlebot was down/uploading to use so much bandwidth, maybe something to do with docker networking and the weird urls.
Amazing though, I never imagined getting ddosed by Google lol. Just goes to show too, one crappy designer off Fiverr can do enough damage to totally ruin your site AND hosting. Now I have to explain to this client how their bad decision is going to cost them more $ to get fixed, and the 10 million urls in their search console is probably going to be an issue as well lol
Btw, I wonder if there's a way for Enhance to more gracefully handle 404s or other such weird uncacheable content/urls? I had a site with two missing fonts that was generating massive load, and another site with missing favicon also generating massive load. It seems even cgroups can't stop 404s from hammering the cpu.