SocialJusticeWarrior
Junior Member
- Jul 18, 2017
- 10
- 7
- 36
So why did this review, as flawed as it may be, get its own thread when it can fit into the existing one?
Which existing one ? there are many, but none exactly like this one.So why did this review, as flawed as it may be, get its own thread when it can fit into the existing one?
This one:Which existing one ? there are many, but none exactly like this one.
That one is mostly Intel. This one is a specific test between AMD and Intel.
Even if they were included it wouldn't make a difference,read the descriptions of the titles they did run.It's a shame that these benchmarks rarely include widely played esport games like lol, dota, or csgo. CSGO is CPU-bound, and players want the highest FPS possible.
World of Tanks isn’t a particularly demanding title but the idea here is to include a wide range of games. Be aware that this game is limited to 120fps and while it's possible to circumvent that cap it’s not something most people are going to bother doing or really need to do.
PlayerUnknown's Battlegrounds
...
It's worth noting that this release is capped at 144fps and I’m not sure if there is a work around to remove it. That said, 144fps is plenty and I can't imagine many players will be able to take advantage of more frames than that in this title.
<<So me running benchmarks decided to not run benchmarks but fps locked titles>> ...Doom has an obvious 200 fps frame cap
He even says it outright for a few titles that they are GPU limited.Being that there's no point in using GPU-limited scenarios to gaming performance of CPUs, we didn't feel the need to gather results for 1440p or 4K.
I have continued to test Ashes of the Singularity Escalation using the crazy preset which pretty much GPU-bottlnecked the Intel CPUs.
The Division is a GPU-limited title
Although For Honor is mostly a GPU-bound game and all three CPUs are able to deliver around the same average frame rate,
(Excellent choice for a benchmark then... )Prey isn't particularly CPU-demanding.
Even if they were included it wouldn't make a difference,read the descriptions of the titles they did run.
<<So me running benchmarks decided to not run benchmarks but fps locked titles>> ...
And if you look at almost all the other ones you can see that even the stock 7700k maxes out the 1080ti in those games...
Good thing he was trying not to show GPU limited scenarios,I bet using FPS locked titles is the best way of achieving this. /s
He even says it outright for a few titles that they are GPU limited.
(Excellent choice for a benchmark then... )
If this benchmark shows you one thing it's that anything above 4 cores is a waste of money if all you want is to game.
If you can't afford a 1080ti then anything above a well clocked i5 (or equivalent) is thrown away money.
The problem with this sort of test is that it is supposition that future games with the sort of mixed settings that people actually play can be mimicked CPU wise by turning graphics settings down on current games, most notably resolution. I've only seen one review try to investigate this, and their finding was that it was a bunch of baloney.If you want to test the prowess behind a CPU, the games must have all GPU-related settings turned to minimum. Texture detail, polygon count, shadow resolution, shaders, and cloth physics (if done on GPU).
Then the CPU-related settings maxed. Shadow distance, draw distance, and the number of lights.
Otherwise, it's a meaningless CPU test, as the entire test itself is buggered.
That would absolutely bottleneck a 1080 ti, especially on a game like PUBG!
If you want to test the prowess behind a CPU, the games must have all GPU-related settings turned to minimum. Texture detail, polygon count, shadow resolution, shaders, and cloth physics (if done on GPU).
Then the CPU-related settings maxed. Shadow distance, draw distance, and the number of lights.
Otherwise, it's a meaningless CPU test, as the entire test itself is buggered.
And that's exactly what the R5 1600 is, an i5 equivalent perfect for anything bellow 1080ti. They sure got this right.If you can't afford a 1080ti then anything above a well clocked i5 (or equivalent) is thrown away money.
I'm saying that even if he tested cs:go he would have found a reason to cap it at say 144fps.So what are you trying to say? That their benchmarks are marred by their choice of titles, some of them FPS-locked and others GPU-limited?
Then given the flaws, how can you say that the benchmark proves "anything above 4 cores is a waste of money"? This is precisely why a CPU-bound game like CSGO should be used, both as a relevant benchmark and to inform on how fast a CPU is needed for 150+ FPS, 200+ FPS, etc. for that specific game since people actually care about getting really high frames for CS.
A benchmark is supposed to show you the absolute maximum that the hardware is capable of,if this was supposed to be a CPU benchmark it would have to show us the maximum capabilities of the CPU and the CPU alone without the GPU or any other part of the system being a limiting factor,it's supposed to set a benchmark of performance not to show you how something would be run on average.But your test is even more meaningless. Sure it may show CPU bottlenecks but who is going to game at lowest graphic level? I mean if you just want to test the number crunching power of a CPU you might as well just run cinebench or fritz chess. Gaming tests should be ran at realistic settings because that is what people actually see in real life.
But your test is even more meaningless. Sure it may show CPU bottlenecks but who is going to game at lowest graphic level? I mean if you just want to test the number crunching power of a CPU you might as well just run cinebench or fritz chess. Gaming tests should be ran at realistic settings because that is what people actually see in real life.
It is pointless benchmark if your software is not optimized for your hardware. All you are testing are bottlenecks in software, not hardware.Showing CPU bottlenecks is the whole point of CPU benchmarking games. Making games into a GPU benchmark to see how a CPU performs? That's not any use. At all.
And games aren't about how many times a CPU can divide and add to an integer each second. Great example: draw call performance.
It is pointless benchmark if your software is not optimized for your hardware. All you are testing are bottlenecks in software, not hardware.
CPU A after release scores 50 and their competitor scores 80 FPS - what is your conclusion in the review?If you make the GPU benchmark GPU centric, it's a GPU benchmark. If you make the CPU benchmark a GPU benchmark, lo' and behold, it's a GPU benchmark.
We want to see how well the CPU performs. Ergo, drive up the load on the CPU, and drive up the load on the driver. How else are you supposed to see how good a CPU performs, other than piling on the settings that tax the CPU?
Software optimization is not indefinite. Hardware capabilities are definite.CPU A after release scores 50 and their competitor scores 80 FPS - what is your conclusion in the review?
After few weeks there comes update to the microcode of the CPU, BIOS of motherboard, and update to the game itself to be optimized for the CPU A.
And the CPU A after the update scores 80 FPS.
What is your conclusion in the end?
This is what I mean: software bottlenecks, caused by unoptimized software. In games you will always be testing for software bottlenecks, not hardware.
Sure, but not by a lot. And who gets a 1080ti to game on 1080p? Once you crank up the resolution the bottleneck disappears. Keep in mind this cpu costs $19 + $5 shipping and can utilizing dirt cheap ram. I'd much rather spend my money on the gpu and even a 1440p monitor. If you look around you can get whole lot, motherboard + 6 cores @ 4G minimum + 24G ram, for $100. I don't think any new CPUs can compete on a value level.
CPU A after release scores 50 and their competitor scores 80 FPS - what is your conclusion in the review?
After few weeks there comes update to the microcode of the CPU, BIOS of motherboard, and update to the game itself to be optimized for the CPU A.
And the CPU A after the update scores 80 FPS.
What is your conclusion in the end?
This is what I mean: software bottlenecks, caused by unoptimized software. In games you will always be testing for software bottlenecks, not hardware.
If you make the GPU benchmark GPU centric, it's a GPU benchmark. If you make the CPU benchmark a GPU benchmark, lo' and behold, it's a GPU benchmark.
We want to see how well the CPU performs. Ergo, drive up the load on the CPU, and drive up the load on the driver. How else are you supposed to see how good a CPU performs, other than piling on the settings that tax the CPU?
Test are meaningless. But opinions about the hardware are worthless.The conclusion is that in the earlier test, CPU A was worse than CPU B in that test. In the later one, CPU A is on par with CPU B. Simple.
The idea of bottlenecks in software making tests worthless is just bizarre. Following that logic, GPU benchmarks are utterly meaningless, due to the affect drivers, shaders, hardware revisions, and game updates can have on GPU performance in a particular game.