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

  • Ian Cutress - Monday, July 24, 2017 - link

    In the way everyone has historically been reporting PCIe lanes, Ryzen only has 16 PCIe lanes intended for graphics, with the other four for the chipset and another four for storage as an SoC. We've repeated this over and over and over again. Same with Threadripper: 60, plus four for chipset. If we're going to start counting PCIe lanes for chipsets (and DMI equivalents) and SoC related PCIe lanes for storage and others, we'll have to go and rewrite the PCIe lane counts for the last several generations of Intel and AMD CPUs.
  • Kalelovil - Monday, July 24, 2017 - link

    If the category is PCIe lanes for graphics that is quite right.
    But by that token doesn't (non cut-down) Broadwell-E/Skylake-E only have 32 lanes intended for graphics, as the switching logic allows for 2x16 and 4x8 configurations.

    Although this is getting quite in-the-weeds. Overall I really appreciate the time and effort put into PC component reviews by the Anandtech staff.
  • FreckledTrout - Monday, July 24, 2017 - link

    I agree with Ian as 4 PCIe lanes are always taken since you are running Ryzen with a chipset with no real way around that. I also would agree with say Skylake-x reporting 4 less PCIe lanes for the DMI link.
  • Trenteth - Wednesday, July 26, 2017 - link

    except Ryzen has 16x GPU lanes, $x to the chipset and 4x diect to an NVMe or U.2 drive. it's 20 PCIe 3.0 lanes off the CPU usable.
  • Notmyusualid - Tuesday, July 25, 2017 - link

    I got 40 lanes on my E5-2690.

    I'm running 4x 1070s on that, and PCIe based storage, and I doubled my throughput by moving the SSD to a riser card (until the 4th GPU went in), which means its back on the m/b.

    Though, you can't notice in everyday use. Oddly.
  • Trenteth - Wednesday, July 26, 2017 - link

    Having the 4x PCIe 3.0 lanes for a NVMe drive is an advantage, it's connected directly to the CPU and bypasses the chipset link which allows more bandwidth for USB/PCIe 2.0 lanes and SATA. I don't agree with you on not counting them.
  • Kalelovil - Monday, July 24, 2017 - link

    Your charts seem to label the i7 7740X with a $329 MSRP.
    In contrast your first page (and Intel ARK) lists a $339-$350 MSRP.

    I assume the former is a mistake?
  • Ian Cutress - Monday, July 24, 2017 - link

    $339 is the 1k tray price - the one that Intel quotes in the price lists and applicable if you buy 1000 OEM CPUs. $350 is MSRP that retailers will apply from their stock from distributors. Add more if you want a cooler. The issue here is that sometimes Intel never quotes an MSRP for some OEM-only processors, and AMD never seem to quote tray/OEM prices for retail parts. I'll edit this and make it clearer.
  • Kalelovil - Monday, July 24, 2017 - link

    Oh, by former I was referring to the $329 in your charts not the $339 on ARK
  • Ian Cutress - Monday, July 24, 2017 - link

    Oops, I misread the price and misread your comment. Graphs should be updated with a cache refresh.

Log in

Don't have an account? Sign up now