Benchmarking Performance: SPECwpc v2.1

Anyone can run wPrime (why would you?) or Geekbench, but more often than not these pre-built synthetic tests are not representative of any user’s workload. This applies even more to professional environments or prosumer workloads, where time is money: if someone interested in hardware cannot pinpoint exactly how the new hardware is going to benefit them, that is $20 of billable time down the drain.

One of the difficulties of a benchmark reviewer is finding relevant benchmarks for the audience at hand. I’ve discussed what AnandTech is and our audience to several high profile software vendors who are in the business of supplying professional grade, critical programs that top technology companies use to produce the next $700 smartphone. These engineers are our readers, and it only seems best that we benchmark something that can assist them in accelerating our workflow. Unfortunately, the almost blanket response from these ISVs is negative, even if the request is for a limited software license in exchange for repeated discussion of the software on AnandTech (and third party benchmark data to assist their customers in hardware purchasing). My last discussions with two major ISVs led to a ‘interesting but we don’t see the value’ response and a ‘we’re doing our own in-house thing’ response respectively. No-one wants to know. Unless you work at one of these companies and want to get in touch.

The fall-back position in this case is to call on SPEC for their Workstation benchmark series. SPECwpc has existed in one form or another for several years, using pre-compiled binaries for a mix of medical, oil-and-gas, engineering, visualization and system level benchmarks. There are over 30 benchmarks, some running multiple copies to keep all the cores busy, and repeated runs offer very good consistency. A full run can take over six hours, making a sizeable increase to even our CPU workflow.

We’re reporting almost all of the subset scores in our benchmarking. Some tests require a GPU, and so we maintain the same RX 460 graphics card on each processor we test, along with the same screen resolution and driver. Ideally we would use professional graphics cards, like AMD’s FirePro range or NVIDIA’s Quadro range, however we currently use four identical RX 460 cards to keep the benchmarks on our test beds continually flowing, and sourcing four of the same pro card on long-term loan is actually fairly difficult.

Because SPECwpc takes so long and is fairly new, we only have results for a few processors so far. This should expand as we continue using this test. We’re likely to limit this test to HEDT processors and above, along with one or two mainstream processors (i7-K, Ryzen 7). For this review, out of the two Intel processors in the title, we only had time to run it on the Core i9-7980XE.

SpecWPC v2.1 - Part 1, Media-2: HandBrake

SpecWPC v2.1 - Part 1, Media-3: LuxRender

SpecWPC v2.1 - Part 1, Media-4: Maya

SpecWPC v2.1 - Part 2, Development-1: Rodinia

SpecWPC v2.1 - Part 2, Development-2: CalculiX

SpecWPC v2.1 - Part 2, Development-3: WPCcfd

SpecWPC v2.1 - Part 2, Development-4: Catia

SpecWPC v2.1 - Part 2, Development-5: Creo

SpecWPC v2.1 - Part 2, Development-6: Showcase

SpecWPC v2.1 - Part 2, Development-7: SNX

SpecWPC v2.1 - Part 2, Development-8: SW

SpecWPC v2.1 - Part 3, Life Sciences-1: Lammps

SpecWPC v2.1 - Part 3, Life Sciences-2: namd

SpecWPC v2.1 - Part 3, Life Sciences-3: Medical

SpecWPC v2.1 - Part 4, Financial-1: Monte Carlo

SpecWPC v2.1 - Part 4, Financial-2: Black Scholes

SpecWPC v2.1 - Part 4, Financial-3: Binomial

SpecWPC v2.1 - Part 5, Energy-1: FFTW

SpecWPC v2.1 - Part 5, Energy-2: Convolution

SpecWPC v2.1 - Part 5, Energy-3: Energy-03

SpecWPC v2.1 - Part 5, Energy-4: srmp

SpecWPC v2.1 - Part 5, Energy-5: Kirchhoff Migration

SpecWPC v2.1 - Part 5, Energy-6: Poisson

SpecWPC v2.1 - Part 6, General-1: 7-Zip

SpecWPC v2.1 - Part 6, General-2: Python

SpecWPC v2.1 - Part 6, General-3: Octave

Benchmark Overview Benchmarking Performance: PCMark 10
Comments Locked

152 Comments

View All Comments

  • mapesdhs - Monday, September 25, 2017 - link

    Ian, thanks for the great review! Very much appreciate the initial focus on productivity tasks, encoding, rendering, etc., instead of games. One thing though, something that's almost always missing from reviews like this (ditto here), how do these CPUs behave for platform stability with max RAM, especially when oc'd?

    When I started building oc'd X79 systems for prosumers on a budget, they often wanted the max 64GB. This turned out to be more complicated than I'd expected, as reviews and certainly most oc forum "clubs" achieved their wonderful results with only modest amounts of RAM, in the case of X79 typically 16GB. Mbd vendors told me published expectations were never with max RAM in mind, and it was "normal" for a mbd to launch without stable BIOS support for a max RAM config at all (blimey). With 64GB installed (I used two GSkill TridentX/2400 4x8GB kits), it was much harder to achieve what was normally considered a typical oc for a 3930K (mab was the ASUS P9X79 WS, basically an R4E but with PLEX chips and some pro features), especially if one wanted the RAM running at 2133 or 2400. Talking to ASUS, they were very helpful and advised on some BIOS tweaks not mentioned in their usual oc guides to specifically help in cases where all RAM slots were occupied and the density was high, especially a max RAM config. Eventually I was able to get 4.8GHz with 64GB @ 2133. However, with the help of an AE expert (this relates to the lack of ECC I reckon), I was also able to determine that although the system could pass every benchmark I could throw at it (all of toms' CPU tests for that era, all 3DMark, CB, etc.), a large AE render (gobbles 40GB RAM) would result in pixel artefacts in the final render which someone like myself (not an AE user) would never notice, but the AE guy spotted them instantly. This was very interesting to me and not something I've ever seen mentioned in any article, ie. an oc'd consumer PC can be "stable" (benchmarks, Prime95 and all the rest of it), but not correct, ie. the memory is sending back incorrect data, but not in a manner that causes a crash. Dropping the clock to 4.7 resolved the issue. Tests like P95 and 3DMark only test parts of a system; a large AE render hammered the whole lot (storage, CPU, RAM and three GTX 580s).

    Thus, could you or will you be able at some point to test how these CPUs/mbds behave with the max 128GB fitted? I suspect you'd find it a very different experience compared to just having 32GB installed, especially under oc'd conditions. It stresses the IMCs so much more.

    I note the Gigabyte specs page says the mbd supports up to 512GB with Registered DIMMs; any chance a memory corp could help you test that? Mind you, I suspect that without ECC, the kind of user who would want that much RAM would probably not be interested in such a system anyway (XEON or EPYC much more sensible).

    Ian.
  • peevee - Monday, September 25, 2017 - link

    "256 KB per core to 1 MB per core. To compensate for the increase in die area, Intel reduced the size of the size of the L3 from 2.5 MB per core to 1.375 MB per core, keeping the overall L2+L3 constant"

    You might want to check your calculator.
  • tygrus - Monday, September 25, 2017 - link

    Maybe Intel saw the AMD TR numbers and had to add 10-15% to their expected freqs. Sure, there is some power that goes to the CPU which ends up in RAM et. al. but these are expensive room heaters. Intel marketing bunnies thought 165w looked better thn 180w to fool the customers.
  • eddieobscurant - Monday, September 25, 2017 - link

    Wow! Another intel pro review. I was expecting this but having graphs displaying intels perf/$ advantage, just wow , you've really outdone yourselves this time.

    Of course i wanted to see how long are you gonna keep delaying the gaming benchmarks of intel's core i9 due to mess rearrangement horrid performance. I guess you're expecting game developers to fix what can be fixed. It's been already several months, but on ryzen you were displaying a few issues since day 1.

    You tested amd with 2400mhz ram , when you know that performance is affected with anything below 3200mhz.

    Several different intel cpus come and go into your graphs only to show that a different intel cpu is better when core i9 lacks in performance and an amd cpu is better.

    Didn't even mention the negligent performance difference bettween the 7960x and 7980xe. Just take a look at phoronix review.

    Can this site even get any lower? Anands name is the only thing keeping it afloat.
  • mkaibear - Tuesday, September 26, 2017 - link

    Erm, there are five graphs on the performance/$ page, and three of them show AMD with a clear price/$ advantage in everything except the very top end and the very bottom end (and one of the other two is pretty much a tie).

    ...how can you possibly call that a pro-Intel review?
  • wolfemane - Tuesday, September 26, 2017 - link

    And why the heck would you want game reviews on these CPUs anyways? By now we KNOW what the results are gonna be and they won't be astonishing. And more than likely will be under a 7700k. Game benchmarks are utterly worthless for these CPUs and any kind of s surprise by the reader in their lack of overall performance in game is the readers fault for not paying attention to previous reviews.
  • Notmyusualid - Tuesday, September 26, 2017 - link

    Sorry to distract gents (and ladies?), and even though I am not a fan of liquid nitrogen, here:

    http://www.pcgamer.com/overclocked-core-i9-7980xe-...
  • gagegfg - Tuesday, September 26, 2017 - link

    EPYC 7551P vs core i9 790XE

    That is the true comparison, or not?
    $2000 vs $2000
  • gagegfg - Tuesday, September 26, 2017 - link

    EPYC 7551P vs core i9 7980XE

    That is the true comparison, or not?
    $2000 vs $2000
  • IGTrading - Tuesday, September 26, 2017 - link

    That's a perfectly valid comparison with the exception of the fact that Intel's X299 platform will look completely handicapped next to AMD's EPYC based solution and it will have just half of the computational power.

Log in

Don't have an account? Sign up now