It's other way round. In general, higher core counts for OLTP workload ( if there's no DB licensing constraint) and higher CPU clocks for DWH and reporting serversIt really depends on your specific work load. Higher clocks are a benefit for transactional work while higher core counts and more pcie throughput are a huge advantage for data warehouses and reporting servers if the app is properly written and the server properly configured.
Inserts and updates are single threaded. Faster clocks and faster disks mean you can get to a point where you release the locks sooner, thus reducing contention and increasing transaction throughput. This does not show up in tests like TPCC because there is less than 2% cross referrencing between queries which makes for artificially low contention compared to almost all real life databases.It's other way round. In general, higher core counts for OLTP workload ( if there's no DB licensing constraint) and higher CPU clocks for DWH and reporting servers
I would be really interested in you filling this idea out with specifics as to why you believe this true. I remember hearing all the bull about hadoop and data lakes, so I am a bit of a skeptic when I see new technologies pushed without any logic or details other than "I say it". My interest is genuine and not hostile - I have people asking me about snowflake and before I take a few months learning it deep, I'd like to know why I should. I am not asking for an exhaustive long post, just a 40 floor elevator pitch (2 minutes, throw fast balls).If its for OLAP, do yourself a favor by looking into Snowflake or Synapse/Databricks. Its a better solution overall.