The AMD 2nd Gen Ryzen Deep Dive: The 2700X, 2700, 2600X, and 2600 Tested
by Ian Cutress on April 19, 2018 9:00 AM ESTCPU Web Tests
One of the issues when running web-based tests is the nature of modern browsers to automatically install updates. This means any sustained period of benchmarking will invariably fall foul of the 'it's updated beyond the state of comparison' rule, especially when browsers will update if you give them half a second to think about it. Despite this, we were able to find a series of commands to create an un-updatable version of Chrome 56 for our 2017 test suite. While this means we might not be on the bleeding edge of the latest browser, it makes the scores between CPUs comparable.
All of our benchmark results can also be found in our benchmark engine, Bench.
SunSpider 1.0.2: link
The oldest web-based benchmark in this portion of our test is SunSpider. This is a very basic javascript algorithm tool, and ends up being more a measure of IPC and latency than anything else, with most high-performance CPUs scoring around about the same. The basic test is looped 10 times and the average taken. We run the basic test 4 times.
Mozilla Kraken 1.1: link
Kraken is another Javascript based benchmark, using the same test harness as SunSpider, but focusing on more stringent real-world use cases and libraries, such as audio processing and image filters. Again, the basic test is looped ten times, and we run the basic test four times.
Google Octane 2.0: link
Along with Mozilla, as Google is a major browser developer, having peak JS performance is typically a critical asset when comparing against the other OS developers. In the same way that SunSpider is a very early JS benchmark, and Kraken is a bit newer, Octane aims to be more relevant to real workloads, especially in power constrained devices such as smartphones and tablets.
WebXPRT 2015: link
While the previous three benchmarks do calculations in the background and represent a score, WebXPRT is designed to be a better interpretation of visual workloads that a professional user might have, such as browser based applications, graphing, image editing, sort/analysis, scientific analysis and financial tools.
Facebook
Twitter
RSS
545 Comments
View All Comments
Luckz - Monday, April 23, 2018 - link
PB2/XFR2 seems to be all the overclocking anyone would want to do on Ryzen 2xxx (besides LN2 and other non-sustainable things)werpu - Friday, April 20, 2018 - link
Ahem those initial results were meltdown only and January, there have been a boatload of fixes since then on both the meltdown and spectre side. So the data is not correct anymore. Even in January VMs etc.. everything I/O intensive already encountered a serious performance hit.Crazyeyeskillah - Friday, April 20, 2018 - link
Those reviews haven't rerun the intel chip parts, hence the dated data.Azix - Thursday, April 19, 2018 - link
They used a 1080 in these tests. maybe thats a factor5080 - Thursday, April 19, 2018 - link
I think what you're seeing with the other reviews is old database information being used without the spectre and meltdown patches. They only say that Ryzen+ was tested with the latest patches, but it dosn't say that they retested all the Intel systems with the BIOS fix and patches applied.Ryan Smith - Thursday, April 19, 2018 - link
All of our Intel systems were re-run with the full Smeltdown fixes for this review.wicketr - Thursday, April 19, 2018 - link
It's be interesting to have an article running all these tests pre and post patches to show how much they affect the system. There seems to be a lot of confusion about how bad it is.Ryan Smith - Thursday, April 19, 2018 - link
It's definitely something we're intending to mine from the data later, after we're over this launch hump.5080 - Thursday, April 19, 2018 - link
That's what I thought and what Chris113q doesn'r realize.hescominsoon - Thursday, April 19, 2018 - link
Chris,You need to take into account the latest system/bios patches for meltdown/spectre as well. Anandtech is not manipulating the results. Just because they get "different" results from "everybody else"(especially when you fail to cite the differences), strains your credibility.