I think 16-32 is the sweet spot. For specific use case I could see 64. But beyond that it would be <.1% of users. Like u would want a thread ripper or 2s at that point
If you have complex virtual setups (or use Chrome, according to some, I won't known since I barely touch it these days) then you might need it.
- VMs for testing eat up memory fast. - A deep disk IO cache dramatically speeds up some workloads, even if processes aren't allocating the memory themselves. - Running a bunch of microservices locally (we have a webpack-based app that eats 16GiB easy - yes, yes... we're working on it).
I think 64 is a bit extreme these days for a personal computer if you're not running a stack of VMs. Servers are a different story, of course.