Faster CPUs won't change that, same as in the last 20 years.
> Faster CPUs won't change that, same as in the last 20 years.
In the last 20 years we've been throwing more and more hardware at the problem, eventually we'll hit a wall and start conserving those precious cycles.
Really? The developers' fault? Whose time are we talking about here?
The company's time? In workplace development, it's managers putting down on the development effort that goes towards optimization / performant design - and not for crazy reasons, simply because in many market conditions and applications, it looks like throwing money away on the balance sheet.
If you're talking about open source projects, any of a developers' time we get is gratis; this would be a pretty good example of looking a gift horse in the mouth.
Would you use this argument to excuse software bugs? What about security holes and data leaks? Besides, the 80/20 rule applies, i.e., a little more effort spent on performance goes a long way towards a better user experience.
> If you're talking about open source projects [...]
Interestingly, this problem is less prevalent in the OSS world, because C and C++ is still very widespread there.
The perf difference between my 2500K and my 6600K is not noticable.
CPUbench
2500k: 6400
6600k: 7921
That's a 20% improvement which doesn't sound like much on paper, but in real world testing that means about double the FPS for higher-end video cards at high res due to the older 2500k design lacking optimizations and other issues holding back those cards.
http://forums.joinsquad.com/topic/5973-my-2500k-vs-6700k-upg...
Lastly, gamers would most likely opt for the i7 6700k which benches at 11000, so almost double that of the 2500k.
On CPUbench, there's a big difference between i5 and i7 parts, and going to a i7 that's generations old gets you better scores than a current top-of-the-line i5.
In some [1] cases that can make quite a bit of difference, up to almost 2x.
[1]: Real improvement is of course anywhere between none and 2x. A lot of software (most even?) is still not using AVX2 at all. Sorting, memory block operations (strlen, memcpy, etc.) and operations that need to do integer math on big chunks of data can benefit significantly. Some real world code I wrote saw up to ~1.9x improvement on systems with sufficient memory bandwidth.
also: my 2011 sandy bridge (2600k or 2700k, at work so can't check) does fine. these days the gpu is the major arbiter of gaming performance.
While GPU is a MAJOR arbiter, CPU can bottleneck you too and it can hit you in the FPS. Years ago my gaming PC had inexplicably low FPS for the GPU it was using, and GPU utilization wasn't anywhere near 100% but CPU was... pop in a new chip+mobo and gaming was waaaay more enjoyable.
There are subtle differences in how bottlenecked GPU vs CPU acts in most games, but they're there.
In most modern games, a better CPU may yield a 10 FPS improvement, while a better GPU for the same price would yield 3x that.
But I suppose it's accurate to say, in general terms and given the kinds of games that are currently most popular, GPU bottlenecking is much more common.
I don't think it's a compelling argument for CPU being the bottleneck when your example is an unoptimized game with a sloppy codebase.
> throwing hardware at problems when you can't fix em in software
DF's problems can be fixed in software, it's just that the creator chose not to. He likes spending his time adding more features instead, performance be damned.
Not that I blame him, he can do as he pleases with his own project.
In the early 2000's, buying a new processor every year would yield noticeable returns in gaming performance. Once we entered the console port life cycle (circa 2008), where the performance of the dominant consoles defined what developers put in games, I found that from 2010-2014 I was able to use the same processor (and not a top of the line one) with no trouble, and only an intermediate graphics card upgrade.
I'm now on the core that I bought in 2014, and I honestly expect it to be good until 2020. We'll see a bit more get juiced out of graphics cards, but we're nearing a stage where the cost of making graphics good enough to overwhelm modern graphics cards will be so high that it won't make sense from a cost/benefit perspective. At that point, I expect CUDA applications to be the driving force behind graphics card R&D.
I'm running a Haswell i7 in my gaming machine and looking at the numbers I'll maybe get a ~3% bump by "upgrading" to Skylake. No thanks.
Another factor to take into consideration is that people change gpu more often than cpu (I would blame intel and their sockets policies but I dont know) so it is obvious you target the lower common denominator which is gonna be the cpu therefore games that don't use lots of cpu to begin with.
Last argument, cpu usage in games can't really be scaled like gpu usage, you can turn down shadows at best but a game is gonna always use that much cpu, being again thelowest common denominator.