Yeah. Back in the 90s, especially in the days of software rendering, a combination of overclocking and config tweaking was often the different between "playable

Yeah. Back in the 90s, especially in the days of software rendering, a combination of overclocking and config tweaking was often the different between "playable" and "unplayable" framerates for something like Quake. The difference was hugely important. These days, generally, you'll be getting playable frame rates no matter what in modern games. Powering up your rig or your config can help to eliminate stutters, push higher levels of detail, etc. But it's generally not needed just to play the dang game in some kind of baseline reasonable way. A faster CPU would help me write code faster, especially when I'm working on a big hairy Rails monolith or whatever. But when you're working on something that slow, a 10% or even a 50% CPU usually doesn't help that much. You need to address the root causes in the software itself - fixing the test suite or whatever.