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

SunSpider has a single threaded focus, and we see the Kaby Lake-X processors take their spots at the top of the graph.

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

Mozilla too relies on single threaded IPC and frequency. 

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

Octane is an interesting benchmark, requiring cores and ST performance, but mostly the latter. It also seems that either Intel's design is optimized for the benchmark or vice versa, given the substantial difference in performance. There's no way for the benchmark to use all of the threads from AMD, nor the 12 threads in the Core i7-7800X which has a lower single thread performance.

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

WebXPRT is a mix of ST and MT, but still based in the web and relies on ST performance a lot. Given the variable loading on the benchmark, Intel's newest features such as Speed Shift help keep it at the top.

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

176 Comments

View All Comments

  • Gulagula - Wednesday, July 26, 2017 - link

    Can anyone explain to me how the 7600k and in some cases the 7600 beating the 7700k almost consistenly. I don't doubt the Ryzen results but the Intel side of results confuses the heck out of me.
  • PeterSun - Wednesday, July 26, 2017 - link

    7800x is missing in LuxMark CPU OpenCL benchmark?
  • kgh00007 - Thursday, July 27, 2017 - link

    Hi, thanks for the great review. Are you guys still using OCCT to check your overclock stability?

    If so what version do you use and which test do you guys use? Is it the CPU OCCT or the CPU Linpack with AVX and for how long before you consider it stable?

    Thanks, I'm trying to work on my own 7700k overclock at the minute!
  • fattslice - Thursday, July 27, 2017 - link

    I hate to say, but there is clearly something very wrong with your 7700K test system. Using the same settings for Tomb Raider, a GTX 1080 11Gbps, and a 7700k set at stock settings I am seeing about 40-50% better fps than you are getting on all three benchmarks--213 avg for Mountain Peak, 163 for Syria, and 166 for Geothermal Valley. This likely is not limited to just RotTR, as your other games have impossible results--technically the i5s cannot beat their respective i7s as they are slower and have less cache. How this was not caught is quite disturbing.
  • welbot - Tuesday, August 1, 2017 - link

    The test was run with a 1080, not a 1080ti. Depending on resolution, ti's can outperform the 1080 by 30%+. Could well be why you see such a big difference.
  • Funyim - Thursday, August 10, 2017 - link

    No. I'm pretty sure the 7700k used was broken. It worries me as well this was posted without further investigation. Basically invalidates all benchmarks.

Log in

Don't have an account? Sign up now