Retesting AMD Ryzen Threadripper’s Game Mode: Halving Cores for More Performance
by Ian Cutress on August 17, 2017 12:01 PM ESTAnalyzing Creator Mode and Game Mode
In this review, we posted every graph with both the Creator Mode results (as default) and the Game Mode results (as 1950X-GM) for the Threadripper 1950X. There were a number of trends worth pointing out.
The first big answer is that in (almost) every multi threaded benchmark that relied on all the threads pushing out data, Game Mode scored considerably less than Creator Mode. In our test suite, I earmarked 19 different tests that are designed to scale with thread count, and the results ranged from +1% (Octane) down to -48% (Corona) and -45% (LuxMark). To summarize, anything that wanted serious throughput, Game Mode was not the right mode to be in. But anyone could have told you that.
The next element is the single threaded tests in the suite. There are 10 of these if we include the four legacy benchmarks, and for the most part these are all within 5% of the Creator Mode results – some are above and some are below, but nothing majorly drastic. Two of the benchmarks, however, did get significant jumps from using Game Mode: Dolphin (+9%) and Agisoft Stage 3 (+38%). Agisoft is probably a hollow victory as overall that test only gains by 1%.
We do run a few variable threaded loads, and the results here really depend on how much of a parallel task it is. As stated before, Agisoft goes up 1%, and perhaps surprisingly our Compile benchmark goes down 14%. One would have thought that the faster memory latency of Game Mode might counteract the lack of threads, especially when the L3 victim cache is of little use, but overall it would seem that our compile test likes the threads instead. WinRAR is a known memory-loving test, so Game Mode picked up a 3% win, and the web benchmarks that are variable threaded such as WebXPRT also picked up a 9% win.
CPU Gaming Tests
Now we turn to our gaming tests. Because we test six different games with four different GPUs at two different resolutions, and in each case take averages and 99th percentiles, I’m going to present this data in a set of different ways. First, the overall gains based on the resolution:
Game Mode Gains Over Creative Mode | ||
1080p | 4K | |
Average | +0.6% | +0.6% |
99th | +14.3% | +8.0% |
The two elements we can draw here are that Game Mode is beneficial mostly for 99th percentiles, but also it affects 1080p gaming over 4K gaming more.
This next table breaks it down by graphics card:
Game Mode Gains Over Creative Mode | ||
NVIDIA GTX 1080 | 1080p | 4K |
Average | -3.1% | 0.0% |
99th | +1.6% | +1.9% |
NVIDIA GTX 1060 | 1080p | 4K |
Average | -0.6% | +0.1% |
99th | +3.1% | +1.9% |
AMD R9 Fury | 1080p | 4K |
Average | +2.5% | +1.5% |
99th | +26.2% | +14.4% |
AMD RX 480 | 1080p | 4K |
Average | +3.6% | +0.6% |
99th | +25.0% | +14.1% |
Again, the data shows that 99th percentiles fare better over averages, although the AMD cards get a better uplift than the NVIDIA cards.
Now let us break it down by game tests.
Game Mode Gains Over Creative Mode | ||
Civilization 6 | 1080p | 4K |
Average | -2.1% | -1.8% |
99th | -5.3% | -3.1% |
Ashes of the Singularity | 1080p | 4K |
Average | -3.2% | -0.1% |
99th | -2.2% | -0.6% |
Shadow of Mordor | 1080p | 4K |
Average | -0.3% | 0.0% |
99th | -4.5% | +0.1% |
Both Civilization 6 and Ashes of The Singularity slight decreases running in Game Mode, with 4K Civilization even regresses 5% in 99th percentile data. Shadow of Mordor has some gains at 4K, mainly with 99th percentile data, but well within the margin of error.
Game Mode Gains Over Creative Mode | ||
RoTR-1 | 1080p | 4K |
Average | -1.3% | +0.1% |
99th | +4.2% | +0.4% |
RoTR-2 | 1080p | 4K |
Average | +2.4% | +1.8% |
99th | +43.7% | +21.9% |
RoTR-3 | 1080p | 4K |
Average | +2.3% | +1.4% |
99th | +17.9% | +11.7% |
Rise of the Tomb Raider has three test stages, and almost all of them benefit from Game Mode. Again, 99th percentiles go up (+43.7% for the Prophets Tomb test), and 1080p gets the better deal over 4K data.
Game Mode Gains Over Creative Mode | ||
Rocket League | 1080p | 4K |
Average | +0.8% | +1.0% |
99th | +9.1% | +2.9% |
Grand Theft Auto V | 1080p | 4K |
Average | +6.9% | +2.2% |
99th | +49.2% | +29.4% |
The last two games are Rocket League and Grand Theft Auto, with Rocket League getting a small bump in 99th percentiles but GTA jumps up double digits. For GTA, those big number spikes at 1080p come from ~100% gains on AMD cards. Similarly at 4K, while NVIDIA cards get nearly no benefit, AMD cards gain 50-73%.
Conclusions on CPU Gaming
Looking at the overall data, the worst loss was a -10% at 4K for Civilization 6, and it's almost a complete mix of positive and negative results across the 256 data points we tested. The takeaway is that on average Game Mode affects certain games really, really well, like RoTR and GTA, but not games like Ashes or Shadow of Mordor. On average that equates to a +8% boost in 99th percentile frame rates at 4K or a +14% boost in 99th percentile frame rates at 1080p, and mostly limited to AMD cards.
If a user wants to use Threadripper to play certain games when using an AMD card, they should be in Game Mode. There are some losses in some titles, but as a catch all situation, the gains for games where it does work are noticable, espeically at lower resolutions.
How Does it Compare to How We Tested on 16C/16T
Interestingly, the results for almost all benchmarks were lower in 8C/16T mode over 16C/16T mode. Despite moving down to a single die worth of cores, it would appear that having the raw cores at the disposal counteracts most of the cross communication losses, especially if each die of cores preferentially communicates with its own DRAM channels where possible.
In the following table,
On the left is AMD's Game Mode vs Creative Mode.
On the right is SMT disabled vs Creative Mode.
Both non-Creative data sets have NUMA enabled.
For example, at 16C/16T we saw a +4% average FPS improvement at 1080p, but now at 8C/16T this is only 0.6%. Before we had a +26.5% gain in 99th percentile numbers at 1080p, but now this is only +14.3%. The individual game numbers are matched similarly - on the right at 1080p at 16C/16T, we get an ~0.1% difference in the results for Game Mode compared to Creator mode, but on the left at 8C/16T we see an average loss of 3% for some of the tests. In the pure CPU benchmarks, at 16C/16T some benchmarks like Dolphin had a +33% increase, but at 8C/16T it is only a +9% increase.
The only upside to running at 8C/16T over 16C/16T would seem to be power consumption. In 8C/16T Game Mode, we saw an all-thread power consumption of 125W. In the non-SMT mode, this was 170W, closer to the default Creative Mode of 177W. One of AMD's reasons for implementing Game Mode like this was due to certain games not accepting the number of threads on offer - in the situations above, both of the new modes tested have 16 threads, at which point disabling SMT would appear to be preferable for performance.
104 Comments
View All Comments
peevee - Friday, August 18, 2017 - link
Of course. Work CPUs must be tested at work. Kiddies are fine with i3s.Ian Cutress - Sunday, August 20, 2017 - link
https://myhacker.net hacking news hacking tutorials hacking ebooksIGTrading - Thursday, August 17, 2017 - link
It would be nice and very useful to post some power consumption results at the platform level, if we're doing "extra" additional testing.It is very important since we're paying for the motherboard just as much as we pay for a Ryzen 5 or even Ryzen 7 processor.
And it will correctly compare the TCO of the X399 platform with the TCO of X299.
jordanclock - Thursday, August 17, 2017 - link
So it looks like AMD should have gone with just disabling SMT for Game Mode. There are way more benefits and it is easier to understand the implications. I haven't seen similar comparisons for Intel in a while, perhaps that can be exploration for Skylake-X as well?HStewart - Thursday, August 17, 2017 - link
I would think disable SMT would be better, but the reason maybe in designed of link between the two 8 Core dies on chip.GruenSein - Thursday, August 17, 2017 - link
I'd really love to see a frame time probability distribution (Frame time on x-axis, rate of occurrence on y-axis). Especially in cases with very unlikely frames below a 60Hz rate, the difference between TR and TR-GM/1800X seem most apparent. Without the distribution, we will never know if we are seeing the same distribution but slightly shifted towards lower frame rates as the slopes of the distribution might be steep. However, those frames with frame times above a 60Hz rate might be real stutters down to a 30Hz rate but they might just as well be frames at a 59,7Hz rate. I realize why this threshold was selected but every threshold is quite arbitrary.MrSpadge - Thursday, August 17, 2017 - link
Does AMD comment on the update? What's their reason for choosing 8C/16T over 16C/16T?> One could postulate that Windows could do something similar with the equivalent of hyperthreads.
They're actually already doing that. Loading 50% of all threads on an SMT machine will result in ~50% average load on every logical core, i.e. all physical cores are only working on 1 thread at a time.
I know mathematically other schedulings are possible, leading to the same result - but by now I think it's common knowledge that the default Win scheduler works like that. Hence most lightly threaded software is indifferent to SMT. Except games.
NetMage - Sunday, August 20, 2017 - link
Then why did SMT mode show differences from Creator mode in the original review?Dribble - Thursday, August 17, 2017 - link
No one is ever going to run game mode - why buy a really expensive chip and then disable half of it, especially as you have to reboot to do it? It's only use is to make threadripper look slightly better in reviews. Imo it would be more honest as a reviewer to just run it in creator mode all the time.jordanclock - Thursday, August 17, 2017 - link
The point is compatibility, as mentioned in the article multiple times. AMD is offering this as an option for applications (mainly games) that do not run correctly, if at all, on >16 core CPUs.