DuckDuckGo make some of these sorts of numbers public: https://duckduckgo.com/traffic

A single query can hit 100s of CPUs. There's over 60k Google search queries per second, according to some random source found on the internet. That would require 600k CPUs. If it's 1000 machines that's being hit it would require 6M CPUs. Also, Internet traffic is bursty, there's maybe 2-3x more queries in peak times.

My experience with working at a FAANG: I remember a service that was easily dealing with >10M QPS (albeit much simpler queries than a Google search), or some other services continuously processing (reading/writing to disks) > 100 GB/s.

There's A LOT you don't see in FAANG frontends. In particular, the Twitter thread owner suggesting https://developers.google.com/speed/ has no idea where is the slowness coming from.

That being said I'd love to be a Google employee to investigate those queries. Perfect bug reports.