CPU 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.

Web: SunSpider on Chrome 56

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.

Web: Mozilla Kraken 1.1 on Chrome 56

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.

Web: Google Octane 2.0 on Chrome 56

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.

Web: WebXPRT 15 on Chrome 56

Overall, all of our web benchmarks show a similar trend. Very few web frameworks offer multi-threading – the browsers themselves are barely multi-threaded at times – so Threadripper's vast thread count is underutilized. What wins the day on the web are a handful of fast cores with high single-threaded performance.

Benchmarking Performance: CPU Rendering Tests Benchmarking Performance: CPU Encoding Tests
Comments Locked

347 Comments

View All Comments

  • Lolimaster - Friday, August 11, 2017 - link

    Adding useless singe thread benchs for people that will pay $600+ for many cores is plain stupidity like that useless open a pdf test.
  • casperes1996 - Saturday, August 12, 2017 - link

    Why do you bother replying to these, Ian? I love your enthusiasm about what you do, and am happy that you reply to comments, but as you state yourself, no matter what you say, you'll be called a shill on more than a weekly basis by either side no matter what you do. Intel shill, AMD shill, Apple shill, Nvidia shill and so on. There's no stopping it, because you just can't please the people who go into something wanting a specific result. Well, you can if you give them that result, but sometimes, facts aren't what you want them to be, and some people don't accept that.

    Cheers, mate
  • Diji1 - Thursday, August 10, 2017 - link

    You sound like a crazy person.
  • Notmyusualid - Saturday, August 12, 2017 - link

    @ Diji1

    You are correct.

    He is implying just because we want HEDT platforms / chips, that we care nothing for single-threaded performance.

    He is a true AMD fan-boi, as you will see over time.
  • lordken - Thursday, August 10, 2017 - link

    @Johan Steyn: while I agree with you that the Intel piece with PR slide at the top was a little bit lame, I even lolled at "most scalable" part (isn't something like "glued" zen the most scalable design?) I think this review is good and goes also around architecture etc., there were few instances during reading when it seemed odd wording or being unnecessarily polite toward intel's shortcoming/deficit but I cant even remember them now.

    Though I was surprised about power numbers, as Toms measured much higher W for 7900X , 160-200 and with TTF even up to 250-331 , but here 7800/7900x had only ~150W.
    Also this sentence is odd
    "All the Threadripper CPUs hit around 177W, just under the 180W TDP, while the Skylake-X CPUs move to their 140W TDP." move to their? They are above the TDP...why not state it clearly?
  • tamalero - Thursday, August 10, 2017 - link

    Im sratching my head on power consumption as well. Almost all reviewers shows that the i9's consume more than threadripper.

    Could be the motherboard used?

    Some used the Zenith and other reviewers used the ASROCK retail one.
  • smilingcrow - Thursday, August 10, 2017 - link

    Power consumption can vary a lot depending on the type of task and the exact nature of that task.
    So you should expect a lot of variation across reviews.
  • Johan Steyn - Thursday, August 10, 2017 - link

    The amount of tests on games in this review is unbalanced. Also read my reply to Ian.

    Extremely well stated: " unnecessarily polite toward Intel's shortcoming" Sometimes I think these guys think all are complete mindless drones.
  • carewolf - Thursday, August 10, 2017 - link

    It has always been like this here. This was pretty neutral by Anandtech standards, they even admitted it when it was faster.
  • Johan Steyn - Thursday, August 10, 2017 - link

    Please read my response to Ian, I think you are not looking close enough to what is happening here.

Log in

Don't have an account? Sign up now