Benchmarking Performance: 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

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

222 Comments

View All Comments

  • Ian Cutress - Saturday, October 7, 2017 - link

    That was a mistake on my part. On that I'm still mentally in an era where 150 MHz is a 10% gain. My quick mental arithmetic failed.
  • ScottSoapbox - Thursday, October 5, 2017 - link

    It's a shame you didn't compare it to the 7820X. I think it was expected that it would better the 7800X at least to some degree, so the more interesting comparison is how much performance does the added cost of 8 cores get you.
  • Ryan Smith - Thursday, October 5, 2017 - link

    The graphs were already getting ridiculously long. For something like that, be sure to look at Bench: https://www.anandtech.com/bench/product/1904?vs=20...
  • realistz - Thursday, October 5, 2017 - link

    AMD panic mode. Price drop imminent.
  • Anonymous Blowhard - Thursday, October 5, 2017 - link

    Price drop already happened. R7 1700X now USD$300 on Amazon.
  • willis936 - Thursday, October 5, 2017 - link

    I'd like to see the memory testing done on Ryzen done on coffee lake as well. It's clear that 2 DDR4 channels is not enough for 8 cores, at least with AMD's memory subsystem. Is it enough for 6 cores with Intel's memory subsystem? Also please be sure to use a GPU powerful enough to warrant even reporting the gaming results.
  • bharatwd - Thursday, October 5, 2017 - link

    Kabylake is faster than Coffeelake. where is the 15% increase? what is the point of + and ++ iteration when there is no improvement in performance? intel is just burning wafers for no reason. Better for them to go back to tick tock clock and stop wasting resources................
  • SunnyNW - Thursday, October 5, 2017 - link

    Honestly I'm not sure why Intel doesn't just keep fab lines for the 7th gen i5s going and just re-label into the 8th gen i3s and just bin differently, ie higher base/turbo.
  • AleXopf - Thursday, October 5, 2017 - link

    Thanks for the review Ian. Just one question. Why do you think power consumption differs so much with the data from techspot, were the 8700k consumes 190w, and it's on par with the 16c32t 1920x?
  • Ian Cutress - Saturday, October 7, 2017 - link

    Are they testing at-wall power consumption at stock? That might add a bunch.

    Our power numbers are just for the CPU, not the at wall - they are derived from the internal calibration tools that the processor uses to determine its own power P-states, which in effect is directly related to the turbo.

    There seems to be a lot of boards that screw around with multi-core turbo this generation, which may also lead to higher power consumption numbers.

Log in

Don't have an account? Sign up now