Final Words

I remember writing a tepid conclusion to my Sandy Bridge E review almost two years ago. At the time, both the LGA-2011 and LGA-1155 platforms were on the same architecture - Sandy Bridge. My conclusion ultimately boiled down to how much having 6 cores mattered to you. As LGA-2011 was the only way to get more than 4 cores in an Intel desktop system, if you needed the cores it was clearly the better option. For everyone else, the more affordable LGA-1155 route made more sense.

Today, the arrival of Ivy Bridge E does little to change that conclusion. In fact, compared to Sandy Bridge E, the IVB version only adds about 5% better performance, while shaving off around 20W under load. To further complicate matters, while SNB-E launched before Ivy Bridge, Ivy Bridge E shows up months after Haswell's debut for the rest of the desktop space. If you want Ivy Bridge E, you need to be comfortable with the fact that you're buying into an older architecture.


SNB-E (left) vs. IVB-E (right)

Although Haswell didn't break any records when it showed up on the desktop, there are definitely situations where it is clearly faster than even the fastest IVB-E SKU. Anything that doesn't make use of all six cores on a 4960X will likely be faster on a cheaper Haswell based 4770K. My guess is that this covers not only the overwhelming majority of the desktop market, but actually a good portion of the enthusiast desktop community as well.

The other downsides remain intact as well. Intel's X79 chipset remains very dated, even more so now that we have Z87 with Haswell. A fresh coat of paint and updated firmware isn't enough to hide the fact that you only get two 6Gbps SATA ports and no native USB 3.0 ports. All motherboard makers have worked around this by adding a plethora of 3rd party controllers to their motherboards, but I tend to prefer the native Intel solutions from a validation and compatibility standpoint. You also lose QuickSync support as there's no integrated GPU, although the two extra cores do help video transcoding go by a lot quicker.

In what I hope will be less than 22 months, Haswell E will likely fix many of these problems. Until that time comes, your decision is pretty simple. Ivy Bridge E picks up where Sandy Bridge E left off. If you have the money to spend and absolutely need any of the following:

1) More than 4 cores,
2) More than 4 DIMM slots,
3) More than 16 PCIe 3.0 lanes

...then Ivy Bridge E is your only option, and it's not a bad one at that. My biggest complaint about IVB-E isn't that it's bad; it's just that it could be so much more. With a modern chipset, an affordable 6-core variant (and/or a high-end 8-core option) and at least using a current gen architecture, this ultra high-end enthusiast platform could be very compelling. Unfortunately it's just not that today. I understand why (Xeon roadmaps and all), but it doesn't make me any happier about the situation. Instead we're left with the great option that is Haswell/Z87. If what you need falls outside of what Z87 can deliver then you're left with a decent, but very compromised (and pricey) alternative.

Overclocking & Power Consumption
Comments Locked

120 Comments

View All Comments

  • 1Angelreloaded - Tuesday, September 3, 2013 - link

    Can you have a comparison chart please for the 4770k, E5-8core Xenon, 4960X, with benchmarks included. This kind of makes little sense to me X-79 was behind on feature sets like full SATA3 when in reality a lot of these boards will be used as workstation/normal/gaming computers, performance on those boards tends to suffer because lack there of native support. Instead 3rd party chips are used to add extra features which have significant drawbacks. I understand using the socket for 2 gen in order to extend life of boards however 1336 and the next leap to haswell should have been taken, making a board last 2 years with the prime features that defined that generation. This just seams like intel is ignoring its higher end market due to lack of competition out there.
  • sabarjp - Tuesday, September 3, 2013 - link

    Kind of depressing that 3 years of technology only took the compile of Firefox from 23 minutes to 20 minutes. The high-end isn't looking so high these days.
  • dgingeri - Tuesday, September 3, 2013 - link

    So where's the 4820k review? I don't care much about more than 4 cores, but I need more I/O than Haswell offers. (crappy motherboards that offer either 8/4/4 or 8/8/2 are just unacceptable.) I'd like to know how the 4820k overclocks and handles I/O from dual and triple SLi/Crossfire.
  • Eidigean - Tuesday, September 3, 2013 - link

    Visual Studio unfortunately does not compile in parallel the way you might think. In a solution you may have multiple projects. If one project depends on four other projects, those four will be compiled in parallel; one project per thread. Once the four dependencies are built, it can build the fifth; however, that last project will be built single-threaded.

    Xcode and native Android projects (with gcc) can actually build multiple files from one project in parallel. On an i7 with hyperthreading, all eight logical processors can build up to eight files simultaneously. This scales with more cores very nicely.

    In summary, VS builds multiple projects from one solution in parallel, while gcc builds multiple files from one project in parallel; the latter of which is much faster.

    I'm curious now to see the build times of Firefox for Mac on a rMBP with an i7. Eagerly waiting for a 12 core Mac Pro with 24 logical processors.
  • BrightCandle - Tuesday, September 3, 2013 - link

    Visual Studio is a very poor parallel compilation test. GCC with make -p can really utilise a lot more cores but its not very Windows like to use GCC (although I suspect many developers do that).

    I haven't found many Java builds doing well on multiple cores, and neither Scala. Its the unit tests where I get the cores going, I can saturate hundreds of cores with unit tests if I had them, and since I run them in the background on every change I certainly do get a lot of usage out of the extra cores. But a clean compile is not one of those cases where I see any benefit from the 6 cores. Of course I would hope these days we don't do that very often.
  • althaz - Tuesday, September 3, 2013 - link

    It is a poor parallel test, but it is a fantastic real-world test for a lot of devs.
  • madmilk - Tuesday, September 3, 2013 - link

    About 25 minutes here on an 2.6GHz/16GB rMBP. Pretty much as expected for quad Ivy Bridge.
  • bminor13 - Tuesday, September 3, 2013 - link

    Parallel file-level compilation is possible in VS2010 and up with the /MP project switch. This is not enabled by default I believe for compatibility reasons.
  • BSMonitor - Tuesday, September 3, 2013 - link

    A Haswell-E will most likely bring a different pin-count, correct?? So this X79 is a dead end platform any way you look at it. Buying the Quad IVB-E makes almost no sense whatsoever.
  • Casper42 - Tuesday, September 3, 2013 - link

    Most Intel chips use a Tick Tock release cycle. Tick Tock Tick Tock Tick Tock etc
    Tick is an Incremental upgrade. Same socket and largely same design, but reduced lithography (32nm down to 22nm for example). Sometimes new Instructions but often not.
    Tock is an Overhaul upgrade. Uses same Lithography as the previous gen, but is a new internal architecture, often a new Socket, and where most new Instruction sets show up.
    Then you get another Tick.

    Core 2/Conroe was a Tock and was 65nm
    Core 2/Penryn was a Tick and was 45nm
    Core iX/Nehalem was a Tock and was 45nm
    Core iX/Westmere was a Tick and was 32nm
    Core iX/Sandy Br was a Tock and was 32nm
    Core iX/Ivy Bridge is a Tick and is 22nm
    Core iX/Haswell is a Tock and is 22nm

    So to say that X79 is a dead platform should not really be a shock to anyone. They got Sandy and Ivy out of it. Thats 1 Tock and 1 Tick and now its time to move on. They do this exact same thing in the 2P Server market where people spend $10K or more per server. The fact of the matter is the server market has already pretty much learned. Don't bother upgrading that server/machine, just ride it for 3-4 years and then replace it completely. SATA, Memory and CPUs have all changed enough by then you want to reset everything anyway.

Log in

Don't have an account? Sign up now