Intel never quite reached 4GHz with the Pentium 4. Despite being on a dedicated quest for gigahertz the company stopped short and the best we ever got was 3.8GHz. Within a year the clock (no pun intended) was reset and we were all running Core 2 Duos at under 3GHz. With each subsequent generation Intel inched those clock speeds higher, but preferred to gain performance through efficiency rather than frequency.

Today, Intel quietly finishes what it started nearly a decade ago. When running a single threaded application, the Core i7-2600K will power gate three of its four cores and turbo the fourth core as high as 3.8GHz. Even with two cores active, the 32nm chip can run them both up to 3.7GHz. The only thing keeping us from 4GHz is a lack of competition to be honest. Relying on single-click motherboard auto-overclocking alone, the 2600K is easily at 4.4GHz. For those of you who want more, 4.6-4.8GHz is within reason. All on air, without any exotic cooling.

Unlike Lynnfield, Sandy Bridge isn’t just about turbo (although Sandy Bridge’s turbo modes are quite awesome). Architecturally it’s the biggest change we’ve seen since Conroe, although looking at a high level block diagram you wouldn’t be able to tell. Architecture width hasn’t changed, but internally SNB features a complete redesign of the Out of Order execution engine, a more efficient front end (courtesy of the decoded µop cache) and a very high bandwidth ring bus. The L3 cache is also lower and the memory controller is much faster. I’ve gone through the architectural improvements in detail here. The end result is better performance all around. For the same money as you would’ve spent last year, you can expect anywhere from 10-50% more performance in existing applications and games from Sandy Bridge.

I mentioned Lynnfield because the performance mainstream quad-core segment hasn’t seen an update from Intel since its introduction in 2009. Sandy Bridge is here to fix that. The architecture will be available, at least initially, in both dual and quad-core flavors for mobile and desktop (our full look at mobile Sandy Bridge is here). By the end of the year we’ll have a six core version as well for the high-end desktop market, not to mention countless Xeon branded SKUs for servers.

The quad-core desktop Sandy Bridge die clocks in at 995 million transistors. We’ll have to wait for Ivy Bridge to break a billion in the mainstream. Encompassed within that transistor count are 114 million transistors dedicated to what Intel now calls Processor Graphics. Internally it’s referred to as the Gen 6.0 Processor Graphics Controller or GT for short. This is a DX10 graphics core that shares little in common with its predecessor. Like the SNB CPU architecture, the GT core architecture has been revamped and optimized to increase IPC. As we mentioned in our Sandy Bridge Preview article, Intel’s new integrated graphics is enough to make $40-$50 discrete GPUs redundant. For the first time since the i740, Intel is taking 3D graphics performance seriously.

CPU Specification Comparison

CPU

Manufacturing Process

Cores

Transistor Count

Die Size

AMD Thuban 6C

45nm

6

904M

346mm2

AMD Deneb 4C

45nm

4

758M

258mm2

Intel Gulftown 6C

32nm

6

1.17B

240mm2

Intel Nehalem/Bloomfield 4C

45nm

4

731M

263mm2

Intel Sandy Bridge 4C

32nm

4

995M

216mm2

Intel Lynnfield 4C

45nm

4

774M

296mm2

Intel Clarkdale 2C

32nm

2

384M

81mm2

Intel Sandy Bridge 2C (GT1)

32nm

2

504M

131mm2

Intel Sandy Bridge 2C (GT2)

32nm

2

624M

149mm2

It’s not all about hardware either. Game testing and driver validation actually has real money behind it at Intel. We’ll see how this progresses over time, but graphics at Intel today very different than it has ever been.

Despite the heavy spending on an on-die GPU, the focus of Sandy Bridge is still improving CPU performance: each core requires 55 million transistors. A complete quad-core Sandy Bridge die measures 216mm2, only 2mm2 larger than the old Core 2 Quad 9000 series (but much, much faster).

As a concession to advancements in GPU computing rather than build SNB’s GPU into a general purpose compute monster Intel outfitted the chip with a small amount of fixed function hardware to enable hardware video transcoding. The marketing folks at Intel call this Quick Sync technology. And for the first time I’ll say that the marketing name doesn’t do the technology justice: Quick Sync puts all previous attempts at GPU accelerated video transcoding to shame. It’s that fast.

There’s also the overclocking controversy. Sandy Bridge is all about integration and thus the clock generator has been moved off of the motherboard and on to the chipset, where its frequency is almost completely locked. BCLK overclocking is dead. Thankfully for some of the chips we care about, Intel will offer fully unlocked versions for the enthusiast community. And these are likely the ones you’ll want to buy. Here’s a preview of what’s to come:

The lower end chips are fully locked. We had difficulty recommending most of the Clarkdale lineup and I wouldn’t be surprised if we have that same problem going forward at the very low-end of the SNB family. AMD will be free to compete for marketshare down there just as it is today.

With the CPU comes a new platform as well. In order to maintain its healthy profit margins Intel breaks backwards compatibility (and thus avoids validation) with existing LGA-1156 motherboards, Sandy Bridge requires a new LGA-1155 motherboard equipped with a 6-series chipset. You can re-use your old heatsinks however.

Clarkdale (left) vs. Sandy Bridge (right)

The new chipset brings 6Gbps SATA support (2 ports) but still no native USB 3.0. That’ll be a 2012 thing it seems.

I think there are many of us that had the same idea. Unless needing to upgrade due to malfunction or new laptop purchase, holding C2D til past the i-Series was the best move to make; whereas buying into C2D asap was the best move at the time.

Still going to wait for prices to fall and more USB3 adoption. Expected new purchase: mid-2011-mid 2012Reply

Ya know I usually do as you are but was an early adopter of the i7 920. Looking now it seems I made the right choice. I have had 2 years of kickassery and my processor still holds up rather well in this article.Reply

Me too! I've got an e8400 running at 3.9 with almost zero OC know-how and its done me well. I might snap up an i7 if they and their mobos get cheap when sandy bridge has been out a few months... but may well skip that generation all together.Reply

Holy crapola AMD really needs Bulldozer now. Even in heavily threaded video encoding the 2600K at $300 is blowing the 1100T x6 out of the water. This is the the Core 2 Duo vs. A64 X2 all over again. Will Bulldozer be another Phenom, a day late and a dollar short? TLB bug anyone? As a PC enthusiast I really want to see competition to keep prices in check. If I had to upgrade today, I can't see how I could turn down the 2600K...Reply

Yeah, new Intel motherboard models are never cheap. I don't understand why the price remains so high when more an more functionality is moving to the CPU. The other killer is that you need a new board for every Intel CPU update.

Lastly, it's hard to throw the "buy now" tag on it with AMD's new architecture over the horizon. Sure, AMD has a tough act to follow, but it's still an unknown that I think is worth waiting for (if it's a dog, you can still buy Intel). Keep in mind that Bulldozer will have a pretty strong IGP, one that may make decent IGP gaming a reality. It will become a matter of how powerful the x86 portion of the Bulldozer is, and they are trying a considerably different approach. Considering the amount of money you'll be paying, you might as well see how AMD shakes out. I guess it just depends on if what you have today can get you by just a little longer.Reply

You're conflating Bulldozer and Llano there. Bulldozer is the new architecture, coming to the desktop as an 8-core throughput monster. Llano is the first desktop APU, cramming 4 32nm K10.5 cores and a Redwood class GPU onto the die. The next generation of desktop APUs will be using Bulldozer cores.Reply