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

  • Krysto - Monday, September 25, 2017 - link

    Yes, it's total bullshit that they are misinterpreting what TDP is. I imagine this is how they'll get away with claiming a lower TDP than the real one in the 8700k chip, too, which has low base clock speed, but the super-high Turbo-Boost, which probably means the REAL TDP will go through the rough when that Turbo Boost is maximized.

    This is how Intel will get to claim that its chips are still faster than AMD "at the same TDP" (wink wink, nudge nudge).
  • Demigod79 - Monday, September 25, 2017 - link

    "What a load of ignorance. Intel tdp is *average* power at *base* clocks, uses more power at all core turbo clocks here. Disable turbo if that's too much power for you."

    I find it ironic that you would call someone ignorant, then reveal your own ignorance about the TDP and turbo clocks.
  • Spunjji - Monday, September 25, 2017 - link

    It is now, it wasn't before. Wanna bet on how many people noticed?
  • SodaAnt - Monday, September 25, 2017 - link

    I'm quite curious what happens if your system cooling simply can't handle it. I suspect if you designed a cooling solution which only supported 165W the CPU would simply throttle itself, but I'm curious by how much.
  • ZeDestructor - Monday, September 25, 2017 - link

    Strictly speaking, all forms of Turbo boost are a form of vendor-sanctioned overclocking. The fact that measured power goes beyond TDP when at max all-core turbo should really not be all that surprising. The ~36% increase in power for ~31% increase in clocks is pretty reasonable and inline when you keep that in mind. Especially when you factor that there has to have been a bit of extra voltage added for stability reasons (power scales linearly with clocks and current, and quadratically to exponentially with voltage).
  • Demigod79 - Monday, September 25, 2017 - link

    I agree. Everything looked good until that page. 190 watts is unacceptable, and Intel needs to correct this right away - either make the CPU run within the TDP limit, or update the TDP to 190 watts in the specs.
  • HStewart - Monday, September 25, 2017 - link

    It funny that people complain about CPU watts but never about external GPU watts. Keep in mind the GPU is smaller amount of area.
  • artk2219 - Monday, September 25, 2017 - link

    They most certainly do, that is one of the biggest gripes against Vega 64, people do seem to have short memory on how high GPU TDP's used to be however.
  • IGTrading - Tuesday, September 26, 2017 - link

    On a video card, the same manufacturer takes responsibility for the GPU, cooling system, design, PCB, components and warranty.

    On the CPU, you have somebody else designing the cooling system, the motherboard, the power lines and they all have to offer warranty for their components while Intel is only concerned with the CPU.

    If the CPU is throttling or burnt out, they will say "sufficient cooling was not provided" and so on ...

    It is a whole lot different.
  • whatevs - Tuesday, September 26, 2017 - link

    Thermal throttling is not a burn out and not a warranty event, you don't get to warranty your gpu when it throttles under load, cooling warranty does not include cpu/gpu chip performance and
    Intel designed the ATX specification and the electrical specification for the boards.

    You clearly don't know the things you're talking about.

Log in

Don't have an account? Sign up now