A cryogenic cooling system that could let a CPU run at 7 GHz would be doable for about $100K.
But more realistically, there are often a long list of other things that can be done to a legacy DB that have a much bigger bang-for-buck, and are also lower risk.
Try NVMe storage. Databases love low-latency storage.
Are you virtualising this in any way? Don't.
Use a better NIC to cut down latency. Think 200 Gbps Mellanox cards with jumbo frames instead of the built-in Broadcom chip that probably cost $1.50.
Try co-locating the app(s) on the same box with the database to really cut the latency. This works great with modern many-core CPUs like an AMD EPYC. You can often dump everything onto one machine and your latency will go from 1ms to 10μs. That's a 100-fold difference!
Turn off the CPU vulnerability mitigations. This is safe as long as nothing else runs on the same hardware. Boosts some databases up to 50%.
Pin the process threads to specific CPU cores. Some newer Intel Xeons have "preferred cores" that will turbo boost higher than any other core.
Upgrade to the latest CPU to get more instructions per clock. This can have surprisingly beneficial effects.
Or... I dunno... fix the database. Does it even use indexes?
Or are we talking about an unsalvageable 4GL system that had its last update 15 years ago that does everything (storage engine, OLTP, forms UI framework, security, and reports)?
How about instant handoff? I guess that would require running the second box as a slave, so both boxes are running harder than they need to...
Does running one of the old FX-8350/70 at 7+ GHz have any benefit, or is it offset by the per-tick improvements of newer CPUs?
It's weird to think of heavily overclocking stuff in a non-gaming workload for me... stuff like chilled coolant and instability suddenly has completely differnet factors to consider.
Although current rumours suggest 7nm Ocean Cove coming in 2022 with 85% increase of IPC compared to Skylake. I wish we could also make performance node that push through 6Ghz.
If I was been cynical.
Not entirely impossible. Given some of these improvement has been sitting within Intel for years due to the delay in 10nm.
I can make an ALU in an FPGA that only takes in one bit data and adds it. That would take the IPC crown. Is it a useful statement? No. Comparing ARM IPC to x86 IPC is far more complicated than measuring length.
I've taken some measurements of the A13's microarchitecture (mostly, its ROB size), and Apple has a bigger lead here than you'd expect. I don't want to share his data without permission, but the bulk of the code is at [2] and I'd be happy to help anyone able to run code on an iDevice repeat the same measurements.
[1] https://www.anandtech.com/show/14892/the-apple-iphone-11-pro...