FSB Bottlenecks: Is 1333MHz Necessary?

Although all desktop Core 2 processors currently feature a 1066MHz FSB, Intel's first Woodcrest processors (the server version of Conroe) offer 1333MHz FSB support. Intel doesn't currently have a desktop chipset with support for the 1333MHz FSB, but the question we wanted answered was whether or not the faster FSB made a difference.

We took our unlocked Core 2 Extreme X6800 and ran it at 2.66GHz using two different settings: 266MHz x 10 and 333MHz x 8; the former corresponds to a 1066MHz FSB and is the same setting that the E6700 runs at, while the latter uses a 1333MHz FSB. The 1333MHz setting used a slightly faster memory bus (DDR2-811 vs. DDR2-800) but given that the processor is not memory bandwidth limited even at DDR2-667 the difference between memory speeds is negligible.

With Intel pulling in the embargo date of all Core 2 benchmarks we had to cut our investigation a bit short, so we're not able to bring you the full suite of benchmarks here to investigate the impact of FSB frequency. That being said, we chose those that would be most representative of the rest.

Why does this 1333MHz vs. 1066MHz debate even matter? For starters, Core 2 Extreme owners will have the option of choosing since they can always just drop their multiplier and run at a higher FSB without overclocking their CPUs (if they so desire). There's also rumor that Apple's first Core 2 based desktops may end up using Woodcrest and not Conroe, which would mean that the 1333MHz FSB would see the light of day on some desktops sooner rather than later.

The final reason this comparison matters is because in reality, Intel's Core architecture is more data hungry than any previous Intel desktop architecture and thus should, in theory, be dependent on a nice and fast FSB. At the same time, thanks to a well engineered shared L2 cache, FSB traffic has been reduced on Core 2 processors. So which wins the battle: the data hungry 4-issue core or the efficient shared L2 cache? Let's find out.

On average at 2.66GHz, the 1333MHz FSB increases performance by 2.4%, but some applications can see an even larger increase in performance. Under DivX, the performance boost was almost as high as going from a 2MB L2 to a 4MB L2. Also remember that as clock speed goes up, the dependence on a faster FSB will also go up.

Thanks to the shared L2 cache, core to core traffic is no longer benefitted by a faster FSB so the improvements we're seeing here are simply due to how data hungry the new architecture is. With its wider front end and more aggressive pre-fetchers, it's no surprise that the Core 2 processors benefit from the 1333MHz FSB. The benefit will increase even more as the first quad core desktop CPUs are introduced. The only question that remains is how long before we see CPUs and motherboards with official 1333MHz FSB support?

If Apple does indeed use a 1333MHz Woodcrest for its new line of Intel based Macs, running Windows it may be the first time that an Apple system will be faster out of the box than an equivalently configured, non-overclocked PC. There's an interesting marketing angle.

Memory Latency: No Integrated Memory Controller Necessary Power Consumption: Who is the king?
Comments Locked

202 Comments

View All Comments

  • crystal clear - Saturday, July 15, 2006 - link

    Just to remind all that-" Intel decides to release a B2 stepping of its Conroe
    processors.Also
    BEWARE of Engineering samples & reviews based on Engineering samples inlcuded.
  • OcHungry - Saturday, July 15, 2006 - link

    I don’t know if this Q been asked or answered (sorry no time reading 120 posts)
    Bu Mr. Anand, can I kindly ask you couple of concerns:
    1) why don’t we see any reference to temp. under load? Temp. is a crucial factor in deciding wether or not I buy conroe since I live in a very hot climate.
    2)A lot people make reference to 64bit and window vista and that conroe is a 32bit architecture and will not perform as good in 64bit. Is it true? can we have some 64bit benchmarks? It would be great to do this test in multitasking.
    3) I have also noticed (from so many who have had pre-release ES @ XS, and other forums) that overclocked conroe does not correspond directly to performance, unlike A64.
    What I mean is: If A64 is overclocked 20%, the performance increases ~20% 9more or less, in most cases), But have not seen this to hold w/ conroe. So I am wondering what would happen if we put a low end conroe, such as E6400 against A64 4000 x2, 2x1mb cache (same price range after price drop) and overclock them to their limit, using stock cooling, and do the benchmarks (64bit included). The reason I am interested in this type of review is because I am an average end user on budget and would like to know which would give me better price/performance. I think I am speaking for at least 90% of consumers. Not everyone buys $1000 cpu and consumers on budget is detrimental to survival of conroe or AM2 cpus. This alone should give you enough incentive to put together a review oriented around us, the mainstream computer users. We can make or break any chipmaker.
    So please Mr. Anad, can we have another review along those lines described above?
    We greatly appreciate it.
    Thanks,
    ochungry
  • aznskickass - Saturday, July 15, 2006 - link

    Hey ochungry, I believe Xbitlabs did an overclocking comparison between a Conroe E6300 and an A64 X2 3800+, and while they didn't do any 64bit benchmarks, the conclusion is that at stock speeds the E6300 is slightly faster than X2 3800+, and when both are overclocked to the max, E6300's lead increases even more.

    Here is the review/comparison:
    http://xbitlabs.com/articles/cpu/display/core2duo-...">http://xbitlabs.com/articles/cpu/display/core2duo-...
  • OcHungry - Saturday, July 15, 2006 - link

    Those guys @ X-bit lab do not fool me. And I hope Anandtech conducts the same test w/ best suited memory module for “BOTH” platforms. We know (so as Xbitlab knows) that, because of IMC, A64 performs its best @ tightest memory timings. X-bit lab should have used http://www.newegg.com/Product/Product.asp?Item=N82...">This memory module if the test was going to be fair and square. Furthermore A64 3800 x2 @ 3ghz is 10x300, which means DDR2 667 1:1 could have been better to use. This http://www.newegg.com/Product/Product.asp?Item=N82...">DDR2 667 @ 3-3-3-10 would have given about 10% better performance than DDR2 4-4-4-12 that they used. X-bit does not mention anything about memory/cpu ratio. What divider was used? Was it 133/266? Or as close to 1:1 as possible? Sooner or later the truth will prevail when we end users try it for ourselves (oh BTW, not ES), and we will see if xbitlab and others were genuinely interested on behalf of consumers, or the interest destined to ill-fated purpose. Will not accuse anyone, but it all look very fishy.
    I am certain that Mr. Anad will clear all these conspicuous reviews , and hand us another that concerns the consumer’s majority- us average users.
  • IntelUser2000 - Saturday, July 15, 2006 - link

    quote:

    We know (so as Xbitlab knows) that, because of IMC, A64 performs its best @ tightest memory timings. X-bit lab should have used This memory module if the test was going to be fair and square. Furthermore A64 3800 x2 @ 3ghz is 10x300, which means DDR2 667 1:1 could have been better to use. This DDR2 667 @ 3-3-3-10 would have given about 10% better performance than DDR2 4-4-4-12 that they used.


    W-R-O-N-G!!! DDR2-800 at EVEN slower 5-5-5-15 timings is FASTER THAN DDR2-667 3-3-3-10: http://xbitlabs.com/articles/cpu/display/amd-socke...">http://xbitlabs.com/articles/cpu/display/amd-socke...

    Prefer AT's results?: http://www.anandtech.com/cpuchipsets/showdoc.aspx?...">http://www.anandtech.com/cpuchipsets/showdoc.aspx?...

    DDR2-800 is faster. The myth that it performs amazingly better(comparatively) with lower latency is just, a myth. I believe there was a thread in forums that tells exactly that.
  • OcHungry - Sunday, July 16, 2006 - link

    Iguess you don’t understand much about AMD's memory latency, direct connect, and 1:1 ratio.
    It is not like Intel's illusionary, that faster than FSB is better. It is not and is useless. Anad proved it here. But this subject has a tendency to be dragged on for ever by those who don’t understand the concept of IMC. So it's better leave it alone.
    But I still would like to see tightest timing and 1:1 ratio. It is now clear to me that those reviews in favor of Intel, artfully evade this argument/request, knowing it will give AMD advantage over Intel's FSB.
  • aznskickass - Sunday, July 16, 2006 - link

    *sigh*

    How is the AMD disadvantaged if BOTH platforms are reviewed using the same RAM?

    AMD needs ultra low latency DDR2 to attain best performance? Well, bad luck, Intel doesn't , there is no 'deliberate' conspiracy to put AMD in a bad light.

    Look, if you just want to hang on to the notion that AMD has been cheated in the reviews, then go ahead and get your X2 4200+ and see how close you can get to Conroes numbers.

    I'll be using my E6600 @ 3.5GHz+ and laughing at your stupidity.
  • aznskickass - Saturday, July 15, 2006 - link

    I consider Xbitlabs to be one of the more trustworthy sites around, and do note that they are testing mainstream chips, and expensive CL3 DDR2 just doesn't make sense in a budget setup, which further puts Conroe in a good light, as it doesn't require expensive CL3 DDR2 to perform well.
  • sum1 - Friday, July 14, 2006 - link

    A good read. For the editor, I found 4 errors, search the full lines of text below at:
    http://www.anandtech.com/printarticle.html?i=2795">http://www.anandtech.com/printarticle.html?i=2795

    That begin said,
    and H.264 in coding
    as soon as its available
    at the fastest desktop processor we've ever tested
    ("and" would be more readable that "at" in this sentence)
  • JarredWalton - Friday, July 14, 2006 - link

    Thanks. At least one of those (in coding) can be blamed on my use of Dragon NaturallySpeaking and not catching the error. The others... well, they can be blamed on me not catching them too. LOL. The last one is sort of a difference of opinion, and I've replaced the comma with a dash, as that was the intended reading. :)

    --Jarred

Log in

Don't have an account? Sign up now