Overclocking Lynnfield at Stock Voltage: We're PCIe Limited

Remember the on-die PCIe controller? Yep. It's to blame.

Lynnfield is Intel's first attempt at an on-die PCIe controller and it actually works surprisingly well. There are no performance or compatibility issues.



The on-die PCIe controller needs more voltage as you overclock Lynnfield, limiting Lynnfield's stock vt overclocking potential.

Unfortunately the PCIe controller on Lynnfield is tied to the BCLK. Increase the BCLK to overclock your CPU and you're also increasing the PCIe controller frequency. This doesn't play well with most PCIe cards, so the first rule of thumb is to try and stay at 133MHz multiples when increasing your BCLK.

The second issue is the bigger one. As you increase the BCLK you increase the frequency of the transistors that communicate to the GPU(s) on the PCIe bus. Those transistors have to send data very far (relatively speaking) and very quickly. When you overclock, you're asking even more of them.

We know that Bloomfield can easily hit higher frequencies without increasing the core voltage, so there's no reason to assume that Lynnfield's core cannot (in fact, we know it can). The issue is the PCIe controller; at higher frequencies those "outside facing" transistors need more juice to operate. Unfortunately on Lynnfield rev 1 there doesn't appear to be a way to selectively give the PCIe transistors more voltage, instead you have to up the voltage to the entire processor.

Intel knows the solution to Lynnfield's voltage requirement for overclocking, unfortunately it's not something that can be applied retroactively. Intel could decouple the PCIe controller from BCLK by introducing more PLLs into the chip or, alternatively, tweak the transistors used for the PCIe interface. Either way we can expect this to change in some later rev of the processor. Whether that means we'll see it in the 45nm generation or we'll have to wait until 32nm remains to be seen.

The good news is that Lynnfield can still overclock well. The bad news is that unlike Bloomfield (and Phenom II) you can't just leave the Vcore untouched to get serious increases in frequency.

Overclocking: Great When Overvolted, Otherwise... Final Words
Comments Locked

343 Comments

View All Comments

  • snakeoil - Tuesday, September 8, 2009 - link

    what part of stock speed you don't understand?

    if you are going to compare 2 processors both must have a fixed stock speed, if you increase the frequency of one of them by 1Ghz over the stock speed that is illegal.

    or either both have a stock fixed speed to benchmark or both are overclocked.

    overclocking is the same it doesn't matter if it's auto overclocking or manual overclocking.

    we the people demand justice.
    we the people are not stupid.


  • Anand Lal Shimpi - Wednesday, September 9, 2009 - link

    You may find that your desire for fixed speed comparisons will become difficult in the future. Both AMD and Intel are going to be embracing this sort of an approach to clock speeds.

    Overclocking is not the same as what is happening with turbo mode. Overclocking is not officially supported by the manufacturer, it is running a part faster than it was sold at in order to improve performance. If an application crashes because you've overclocked your chip too far that's no fault of the manufacturer.

    Turbo mode runs the chip at a frequency it's guaranteed to work at, it's operating within spec. It simply re-allocates thermal resources; Intel could disable 3 of the cores and sell a Core i7 870 as a 3.6GHz single-core processor, or disable 2 of the cores and sell it as a 3.47GHz processor, or only disable one core and sell it as a 3.2GHz processor. Instead of making the end user choose, instead you get a dynamic processor that can configure itself in real time depending on the workload.

    This is in stark contrast to AMD's Overdrive utility which is actually overclocking. The chips aren't validated at the overdrive speeds and you're thus overclocking. Lynnfield is validated at both its standard clock speed and its turbo speeds, just like Bloomfield. So long as you don't exceed the TDP of the chip, it will work at those turbo frequencies. The things that will prevent it from turboing were outlined in the article.

    Once again, I am not increasing the speed of anything - Lynnfield is simply working as designed. Whether it's in a Dell machine or in a custom build, it will always work this way. It's what the end user will see the moment they turn on a Lynnfield machine. The end user would not see the same from a Core 2 or a Phenom II based machine.

    Take care,
    Anand

  • Jamahl - Wednesday, September 9, 2009 - link

    The problem with this review is it has a bunch of graphs with intel cpus with speeds rated at a lot lower than what they actually are.

    When you show a graph of an i5 @ 2.66 gigahertz beating a 3.4 gigahertz phenom II, that is false and that is a problem. This cpu was not ever at 2.66 gigahertz for any of these tests was it?

    I suggest there is a problem with your reviewer also, not to mention his attitude about 'having a laugh' because i brought up this point?
  • Anand Lal Shimpi - Wednesday, September 9, 2009 - link

    Again, that is the default clock of the processor - in many cases (especially the heavily threaded tests) it will be running at that speed. Turbo mode is dynamic, it's impossible to put down exactly what speed the chip was running at as it'll change throughout each test.

    You might see the chip run at 2.66GHz for several seconds, jump up to 3.46GHz then down to 3.2GHz, up to 3.6GHz and then back down to 2.66GHz all in the course of a single benchmark. It's repeatable, but there's no way to display all of that in a bar chart.

    Take care,
    Anand
  • snakeoil - Wednesday, September 9, 2009 - link

    What you are doing is cheating, and people is not stupid.
    you are saying that lynnfield is faster than phenom 2 because lynnfield is overclocked at least 600 mhz.
    people is not stupid as you think, and what you are doing is outrageous.
    if you are going to benchamark with turbo enabled then you have to overclock phenom 2 at least the same 600 mhz.

    show some respect for your readers. or are you really on intel's payroll?
  • Klober - Wednesday, September 9, 2009 - link

    I am usually very respectful on the AnandTech and DailyTech forums and comments areas, but you sir are exactly as stupid as you are claiming people "is" not. Please read the article from beginning to end before continuing on your unjustified tirade. The processor is being used as intended by the manufacturer - to not test it in this way would be a disservice to the engineers who designed it and the company that produces it.
  • snakeoil - Wednesday, September 9, 2009 - link

    if you dont want to disable turbo the overclock phenom 2 at least 600 mhz.
    just to be fair.
  • Gary Key - Wednesday, September 9, 2009 - link

    "if you dont want to disable turbo the overclock phenom 2 at least 600 mhz.
    just to be fair. "

    You do realize that it takes near zero or sub-zero cooling to run the 965BE in stable manner at 4GHz with a 64-bit OS. When I say stable, I mean 24/7 multi-tasking, not a CPUZ screenshot or a SuperPi 1M bench. AMD has not solved this problem with the current stepping.

    Once again, and for the last time, Intel's turbo function is a standard feature of the processor. AMD will be offering the exact same technology in their next processor family.
  • snakeoil - Wednesday, September 9, 2009 - link

    that's not true.
    we demand justice and fair benchmarks.
    you are losing all credibility and these benchmarks are worthless and unreal.
  • goinginstyle - Wednesday, September 9, 2009 - link

    How many times do they have to respond to you in a logical manner. You should be banned and in some countries that would mean a beheading for being so damn stupid.

Log in

Don't have an account? Sign up now