CPU Tests: Legacy and Web

In order to gather data to compare with older benchmarks, we are still keeping a number of tests under our ‘legacy’ section. This includes all the former major versions of CineBench (R15, R11.5, R10) as well as x264 HD 3.0 and the first very naïve version of 3DPM v2.1. We won’t be transferring the data over from the old testing into Bench, otherwise it would be populated with 200 CPUs with only one data point, so it will fill up as we test more CPUs like the others.

The other section here is our web tests.

Web Tests: Kraken, Octane, and Speedometer

Benchmarking using web tools is always a bit difficult. Browsers change almost daily, and the way the web is used changes even quicker. While there is some scope for advanced computational based benchmarks, most users care about responsiveness, which requires a strong back-end to work quickly to provide on the front-end. The benchmarks we chose for our web tests are essentially industry standards – at least once upon a time.

It should be noted that for each test, the browser is closed and re-opened a new with a fresh cache. We use a fixed Chromium version for our tests with the update capabilities removed to ensure consistency.

Mozilla Kraken 1.1

Kraken is a 2010 benchmark from Mozilla and does a series of JavaScript tests. These tests are a little more involved than previous tests, looking at artificial intelligence, audio manipulation, image manipulation, json parsing, and cryptographic functions. The benchmark starts with an initial download of data for the audio and imaging, and then runs through 10 times giving a timed result.

We loop through the 10-run test four times (so that’s a total of 40 runs), and average the four end-results. The result is given as time to complete the test, and we’re reaching a slow asymptotic limit with regards the highest IPC processors.

(7-1) Kraken 1.1 Web Test

Sizeable single thread improvements.

Google Octane 2.0

Our second test is also JavaScript based, but uses a lot more variation of newer JS techniques, such as object-oriented programming, kernel simulation, object creation/destruction, garbage collection, array manipulations, compiler latency and code execution.

Octane was developed after the discontinuation of other tests, with the goal of being more web-like than previous tests. It has been a popular benchmark, making it an obvious target for optimizations in the JavaScript engines. Ultimately it was retired in early 2017 due to this, although it is still widely used as a tool to determine general CPU performance in a number of web tasks.

(7-2) Google Octane 2.0 Web Test

Speedometer 2: JavaScript Frameworks

Our newest web test is Speedometer 2, which is a test over a series of JavaScript frameworks to do three simple things: built a list, enable each item in the list, and remove the list. All the frameworks implement the same visual cues, but obviously apply them from different coding angles.

Our test goes through the list of frameworks, and produces a final score indicative of ‘rpm’, one of the benchmarks internal metrics.

We repeat over the benchmark for a dozen loops, taking the average of the last five.

(7-3) Speedometer 2.0 Web Test

Legacy Tests

(6-3a) CineBench R15 ST(6-3b) CineBench R15 MT(6-5a) x264 HD 3.0 Pass 1(6-5b) x264 HD 3.0 Pass 2(6-4a) 3DPM v1 ST(6-4b) 3DPM v1 MT

CPU Tests: Encoding CPU Tests: Synthetic and SPEC
Comments Locked

135 Comments

View All Comments

  • mode_13h - Tuesday, August 10, 2021 - link

    > that hot, expensive Gen 4 M.2 NVMe SSD you want to use on your new
    > motherboard will not achieve the speed you paid dearly for.

    None of the 1st gen PCIe 4.0 M.2 NVMe SSDs did, in fact. A lot of them still don't. And if you're not running it at PCIe 4.0, then it's probably also running a bit cooler.
  • alfatekpt - Monday, August 9, 2021 - link

    Currently 5600G and 5600X are at the same price in my country. Should I get the 5600G? I already have a GPU so having an integrated one is only useful in case the GPU breaks or needs to go under warranty and I still can use the PC...
  • mode_13h - Tuesday, August 10, 2021 - link

    I wouldn't get the G. The X is faster in every single benchmark, and sometimes substantially! Plus, you get PCIe 4.0, in case that's ever of interest.

    If you just want a backup GPU, so you're not completely dead in the water, then maybe pick up a used low-end model (especially when GPU prices cool off, a bit). I'm seeing used RX 550's for < $100, which is roughly performance-equivalent.

    If you don't care about performance, then you can go even older. I have a HD 5450 as a sort of last-resort fallback, and those are CHEAP! That's pre-GCN, but I know it still works on Linux. I think it shouldn't be too hard to find something a bit newer that's also cheap, though. Or, if you have some friends who would loan you an obsolete GPU in a pinch, that's also an option worth considering.
  • phoenix_rizzen - Monday, August 9, 2021 - link

    The "Ryzen 5 APUs (65W)" table on page 1 lists the Ryzen 5 CPUs with 8 cores / 16 threads. Should be 6/12 instead.
  • plonk420 - Tuesday, August 10, 2021 - link

    thanks for the core to core latency tests! looks like RPCS3 will definitely benefit from it \o/
  • Oxford Guy - Wednesday, August 11, 2021 - link

    ‘In our largest sub-test, the Intel processors crack on ahead,’

    Did I miss the stuff about performance-per-watt?

    If an Intel chip needs a boatload more power to do the barely faster work, how is that a victory for Intel’s chip?

    Performance-per-watt is important when we’re dealing with today’s 14nm vs. ‘7nm’ situation.

    There should be an entire page devoted to performance-per-watt.
  • mode_13h - Thursday, August 12, 2021 - link

    There is indeed a page on power consumption, but the most revealing charts only compared the three AMD 5000G-series processors to each other. That was a painful omission.

    Intel got included in the peak power chart, but we all know that peak power is hardly the whole story.
  • Oxford Guy - Thursday, August 12, 2021 - link

    ‘There is indeed a page on power consumption’

    Indeed, there is no page on performance-per-watt — and the article continues this site’s erroneous tradition of claiming that getting a slightly higher score in a benchmark whilst using a ton more power constitutes a victory.

    Context is key. These articles should pay more mind to practical context, rather than things like pumping 1.45 volts into Rocket Lake and ignoring power consumption failure (vis-a-vis the competition) when examining a benchmark.
  • mode_13h - Friday, August 13, 2021 - link

    FWIW, I was trying to agree with you. Their "Power Consumption" page had several key omissions.
  • Oxford Guy - Sunday, August 15, 2021 - link

    Regardless... peak power isn’t enough to constitute a page on performance per watt.

Log in

Don't have an account? Sign up now