- Joined
- Sep 17, 2014
- Messages
- 20,902 (5.97/day)
- Location
- The Washing Machine
Processor | i7 8700k 4.6Ghz @ 1.24V |
---|---|
Motherboard | AsRock Fatal1ty K6 Z370 |
Cooling | beQuiet! Dark Rock Pro 3 |
Memory | 16GB Corsair Vengeance LPX 3200/C16 |
Video Card(s) | ASRock RX7900XT Phantom Gaming |
Storage | Samsung 850 EVO 1TB + Samsung 830 256GB + Crucial BX100 250GB + Toshiba 1TB HDD |
Display(s) | Gigabyte G34QWC (3440x1440) |
Case | Fractal Design Define R5 |
Audio Device(s) | Harman Kardon AVR137 + 2.1 |
Power Supply | EVGA Supernova G2 750W |
Mouse | XTRFY M42 |
Keyboard | Lenovo Thinkpad Trackpoint II |
Software | W10 x64 |
Yes, its a RAM test to show how it improves FPS in a game. So, wouldn't more valid testing be to at least use AA at 1080p (which is what most users do that have at least half a clue)? People don't run 1080Ti's at 1080p with no AA. To that end, it is exaggerating the results with an unrealistic testing environment. I don't care what card or CPU is used, 1080p with Ultra/High settings and AA his how people do (who aren't running a 1050, lol).
Why do you have to be CPU bottlenecked? You aren't when playing with normal settings? Why fabricate that environmental variable when testing?
You keep harping on low-end cards with high-end CPUs like it has something to do with this. I can't help how others test, nor is that any justification for testing in an equally lopsided manner (and to be clear, I am referring to HEDT CPUs excluding 7740K and its little brother - I believe testing with a 7700K or 8700K is absolutely fine. Plenty buy this way ). Can we focus on the discussion ?
There is no way everyone will be happy. My only concern is people see this data and think they will achieve the same results at their settings and resolution. They won't. IMO, the best way to test is more realistic running situations. If you are going to use a 1080Ti down to a 1060, at least run at 1080p Ultra/High with gobs of AA, or better yet, 2560x1440. I feel complete testing will test this fabricated environment and something more realistic so users have results closer to where they play. AS this testing stands, people look at it and think they will see these gains where they play, and they won't.
It isn't though. That is what I am saying. Because in many games, you are not cpu bottlenecked unless you rock Sandybridge or lower on Intel and every AMD cpu not named Ryzen. Some are, but then are they actually memory bandwidth limited which is what they are actually testing???? Lots of variables...
Oh well, a never-ending discussion again. Sorry I brought it up.
1. Market share of CPUs has NEVER been an influential factor for reviewers on gaming GPUs. A lot of them used HEDT class CPUs with mainstream GPUs, in fact.
2. You have a fundamentally different approach to 'reviews' it seems. Your reviews are aimed at 'what can I expect in real life' and not at 'what is the raw potential of this component'. Commendable but not realistic. How do you decide what is the 'average use case' and above all, what is 'average' or 'normal'? Its way too abstract especially in the PC world.
3. This different approach of yours, reduces the value of your style of reviewing to that of the simpleton: it is no more than a 'Can I Run this' benchmark focused on a specific component. I hate to break it to you, but in all fairness, we already have crappy websites for that basic info. Why write a whole review and analysis? I won't even read it, honestly. I care a lot more about that raw performance, because that is still relevant in other situations as an indicator of what the fastest solution will be.
We have butted heads on this on multiple occasions but the pattern is clear and again, I believe these are two radically different approaches at work here. Synthetic versus real world. While synthetic still is a valuable data-set 10 years from now, real world only matters today with the current driver, games, components and market reality. In my humble opinion, that is why we now see 'Performance Analysis' per game. Because really, for these real world performance numbers, the per-game basis is so much more valuable.
Focus on what's important for the subject of the article, and clearly divide the two, and there is no need for a never ending discussion on the subject, but instead we do gain more valuable information both for the NOW and future. When you review a component: focus on the component. When you review a game/bench a game: focus on the game.
Last edited: