E5-2695 V3 and E5-2697 V3 Conclusion

Reviewing CPUs that differ only in CPU count or clock speed but are based on similar architectures is predominantly a point and click affair. The CPU with the higher single core frequency does well in response focused benchmarks, and those with more cores with enough memory bandwidth to support them. For Xeons, the price difference for more cores or more frequency never makes much sense if you calculate the difference in terms of power, but becomes more realistic when the time-to-complete for intensive workloads is taken into account. To throw a spanner into the mix, as Johan found in his Haswell-EP testing, Xeons like the E5-2667 v3 exist to take advantage of higher AVX clock speeds due to increased power headroom, accelerating mixed-AVX workloads more than a higher core-count model which has to reduce frequency to compensate. The E5-2667 v3 therefore costs an extra $1000+ over its nearest core counterpart.

The two CPUs we have reviewed today, the E5-2695 V3 and E5-2697 V3, fall directly into Intel’s 2.3-2.6 GHz product line for Xeon E5-2600 V3 CPUs. This comes across as the main segmentation for Intel’s binning process from 8-core to 18-core, with the main differentiator relating to core count and pricing. The difference in 300 MHz comes at the expense of 25W TDP on paper as well as $278 in the back pocket.

An interesting point to note about the 2.3-2.6 GHz stack is the turbo frequencies. Not all SKUs are made similar:

Buying a 2.3 GHz base frequency processor with more cores does several things aside from the price: raise the peak turbo frequency, extend the turbo frequencies across more cores and increase the power consumption. As a result, buying the next CPU up in the stack affords more than just a couple of extra cores – there is both single thread and multithread performance of interest. With this in mind, it might be worth examining the Xeon range from through a MHz lens next generation rather than a core viewpoint.

On the 2.6 GHz graph, the 8-core model starts with the higher turbo frequency and has a more regular decline, while the 10-core and 12-core are evenly matched until the 12-core reduces to a lower all-core turbo. The peak turbo frequency again lies with the parts with more cores, and thus ends up with more TDP and cost more to purchase.

I showed the 2.3 GHz graph to some of the other editors and they pointed out the obvious differentiator: the 16 core CPU has a significant MHz advantage from 1-8 core loading over the 14C variant. For any software with a variable threaded load, the 16 core would push the performance and be on par with the 18 core. The price difference between the 14 core model and the 16 core model is nearly $1000, making budgets and workloads being important factors in this decision. The prevalence of multithreaded code is server and workstation environments make the frequency difference extremely important, especially when it comes to the types of workloads that have frequent memory delays and accesses.

This is apt, as our next element of Xeon coverage will be on the 16-core E5-2698 V3. If we can obtain a sample of the E5-2699 V3 as well, it will complete the set.

Gaming Benchmarks


View All Comments

  • Wolfpup - Tuesday, November 25, 2014 - link

    This is awesome :-D I'll never get to touch one of these, even at work, but it's still ridiculous fun to read about them, much less see game benchmarks on them.

    (Imagine a game actually designed for 18 Haswell cores LOL)

    I'd loooove to run Folding @ Home across that many cores!
  • daresystem - Monday, December 15, 2014 - link

    It's interesting, I am actually system builder, so this information is very useful for me. Why you didn't benchmark it with VMWare? I've been using S2600CP for entire my client for year, and I just curious with the performance this processor in real Server usage.
    Thank you.
  • jackdgalloway - Friday, June 12, 2015 - link

    Regarding the "snoop mode". I got two dual socket, Intel(R) Xeon(R) CPU E5-2697 v3 boxes and found them performing 15% slower on a finite element code than the previous generation dual socket Intel(R) Xeon(R) CPU E5-2697 v2 boxes we had. After much investigation I found the snoop mode was set to early snoop, changing to "cluster on die" sped up the FEA simulation immensely, with that one change the box then outperforming the V2 counterpart by 25%. This was great, however I'm still encountering one problem. I have a monte carlo particle transport code (not a matrix dominant code) whose performance was unaffected by this change, and is still 50% slower than the v2 counterpart. All that said, any intuition on why might be and either troubleshooting thoughts, architecture differences that could cause this, or any other BIOS settings to try? Reply
  • lucien_br - Sunday, March 5, 2017 - link

    Xeon V3 with actual game BF1:

Log in

Don't have an account? Sign up now