Tuning Memory Subsystem Performance

Earlier, we talked about the importance of first testing your motherboard's memory subsystem before moving to the CPU. When you think about it, the reason is clear. Encountering an error while testing blindly provides absolutely no helpful information as to the source of the problem. Since both the CPU and memory stability are dependent on the FSB it only makes sense that we remove them from the equation and first tune our motherboard at our target FSB. This is accomplished by setting the target FSB (we recommend you start at 400 MHz) in the BIOS, making certain to select a CPU multiplier which places the final processor frequency at or below the default value. Next, loosen up all primary memory timings and set the memory voltage to the modules' maximum rated value. Assuming the system is in good working order, we can now attribute all observed errors to discrepancies in the MCH settings and nothing else.


Preparing to run Prime95's blend test for the first time

Boot the system in Windows and launch an instance of Prime95. From the menu select "Options" then "Torture Test…" and highlight the option to run the blend test (default). Now click "OK" to start the test. The blend test mode runs larger FFT values, meaning the processor must rely heavily on the memory subsystem when saving and retrieving intermediate calculation results. Although a true test of system stability would require many hours of consecutive testing, in the interest of time let the program execute for a minimum of 30 minutes.

If you encounter no errors (and the system is indeed still running), you can consider the memory subsystem "stable" at this point. If this is not the case, exit Windows, enter the BIOS, and try slightly increasing the MCH voltage. Repeat this process until you find you can complete (at least) a 30 minute run with no errors. If for some reason you find that increasing the MCH, voltage continues to have no effect on stability, or you have reached your allowable MCH voltage limit, you may be attempting to run the MCH higher than what is achievable under stable conditions. Setting Command Rate 2N - if available in the BIOS - loosening tRD, or removing two DIMMs (if you are running four) may help. If you find modifications to those items allows for completion of an initial Prime95 test, be sure to continue the testing by reducing the MCH voltage until you find the minimum stable value before moving on.

On the other hand, if you find that you can comfortably complete testing with additional MCH voltage margin to spare then you are in a good position to dial in some extra performance. Whether or not you wish to depends on your overall overclocking goal. Generally, more performance requires more voltage; this means more heat, higher temperatures, and increased operating costs. If efficiency is your focus, you may wish to stop here and move on to the next phase in tuning. Otherwise, if performance is your only concern, decreasing tRD is a great way of improving memory bandwidth, albeit usually at the expense of a higher MCH voltage.

In the end, as long as the system is stable, you are ready to move on to the next step. The insight necessary to determine just what to change and the effect if will have on stability and performance is something that comes only with experience. We cannot teach you this and experimenting further at a later time will help you sharpen these skills.

The Origins of Static Read Control Delay (tRD) Select a Memory Divider and Set Some Timings
Comments Locked

56 Comments

View All Comments

  • Aivas47a - Wednesday, December 19, 2007 - link

    Great article. You guys have really been distinguishing yourselves with in-depth work on overclocking the last few months: exploring obscure bios settings, tinkering with "extreme" cooling -- keep it up!

    My experience with a qx9650 so far is very similar to yours: easy scaling to 4 ghz, difficult scaling after that with 4.2 ghz being the practical max for regular operation (folding, etc.).

    One issue I will be interested to see you address in the future is fsb overclocking on yorkfield. So far I am seeing yorkfield top out at lower fsb (450-460) than was possible for kentsfield on a comparable P35 or X38 platform. That is not so significant for the unlocked Extreme Edition chips, but could make it difficult to achieve the magic 4 ghz with the q9550 and especially the q9450.
  • Aivas47a - Wednesday, December 19, 2007 - link

    Great article. You guys have really been distinguishing yourselves with in-depth work on overclocking the last few months: exploring obscure bios settings, tinkering with "extreme" cooling -- keep it up!

    My experience with a qx9650 so far is very similar to yours: easy scaling to 4 ghz, difficult scaling after that with 4.2 ghz being the practical max for regular operation (folding, etc.).

    One issue I will be interested to see you address in the future is fsb overclocking on yorkfield. So far I am seeing yorkfield top out at lower fsb (450-460) than was possible for kentsfield on a comparable P35 or X38 platform. That is not so significant for the unlocked Extreme Edition chips, but could make it difficult to achieve the magic 4 ghz with the q9550 and especially the q9450.
  • Doormat - Wednesday, December 19, 2007 - link

    Though its somewhat disappointing on the rumors that Intel has postponed the launch of their QuadCore desktop chips from January to March.
  • Sunrise089 - Wednesday, December 19, 2007 - link

    I agree with everyone else - really top notch stuff here.

    1 glaring typo though, from the first page: "Moving to a smaller node process technology allows for the potential of one or two things to happen. " - the "or" should be an "of"
  • ChronoReverse - Wednesday, December 19, 2007 - link

    It seems that ATI cards have less of a drop going from XP to Vista (down to zero and even negative sometimes). It might be instructive to use that for the charts that compare Vista to XP for 3D (e.g., the 3Dmark06 benchmark).
  • melgross - Wednesday, December 19, 2007 - link

    Capacitors have their capacitance turned into reactance at higher frequencies. Anything that qualifies, in a circuit, as a capacitor, such as two wires riding in parallel, will have, to a greater or lesser extent, the same problem in the design.

    Reactance rolls off high frequencies. More power is required to offset that.

    This is the same problem whether dealing with low frequencies in an audio circuit (where it may be less of a problem), or a high performing computer. It's almost impossible to eliminate all stray capacitance from a circuit, and more circuitry becomes capacitive at higher frequencies. This will only increase as a problem as we get to smaller processes, such as 32nm.
  • andyleung - Wednesday, December 19, 2007 - link

    I am very interested in the performance of these new CPUs. They are Quad-Core and they are good enough to perform some heavy duty business tasks. Wondering how they work with JEE performance.
  • BLHealthy4life - Wednesday, December 19, 2007 - link

    This article is a perfect example of what makes Anandtech so great. Anandtech has the most brilliant and most technically savvy guys on the internet.

    Very rarely will you fine any other website review pieces of hardware with such intricate detail for hardware specs and the technology behind it.

    Great work guys!
    BL
  • kkak52 - Wednesday, December 19, 2007 - link

    really an informative article.... good work!
  • Bozo Galora - Wednesday, December 19, 2007 - link

    A 10+ article, especially the vdroop section.
    Its nice to see something on AT like the old days thats cuts through the BS and actually gives real usable info.
    Quite a tour de force.
    Nice work.

Log in

Don't have an account? Sign up now