General Memory Performance Scaling and Command Rate

Fiddling with the BIOS to see what works and what does not is all well and good but meaningless unless we have A way to quantify the results. To that end, we've done our best to tabulate the details of our testing and present the following.

Memory Performance - Scaling

Before delving into more advanced discussions let's first review what we already know about typical memory scaling. In this graph, we show how memory responds to a simple change in base operating frequency. Here we can see the memory responds just as we expect - higher frequencies bring about higher bandwidths.

The green lines represent actual data points, collected with timings of 8-8-8-15, a Static Read Control Delay of 7 and Command Rate 1N. The blue lines represent extrapolated data points - i.e. we did not measure these values directly but rather scaled existing test results to create additional information for comparison purposes. This is an important detail to note as this means we extrapolated the data points in the context of our original tests (the same timings, etc.). While this isn't 100% accurate, it does provide a very good estimate for the timings you would most likely set at these particular speeds.

The result is an unadulterated illustration of memory read performance with frequency being the only variable - just as we intended. This also gives us the ability to predict how our memory would perform should we run it at DDR-2000 with 8-8-8-15 timings. While some choose to do this by pumping excessive voltage through their memory modules, we feel our method is safer as we do not risk damaging our expensive DDR3. Future DDR3 will likely be able to reach these higher performance settings at more reasonable voltages, however.

Our ASUS P5E3 Deluxe exhibited an amazing memory scaling range, allowing us to run our memory 1:1 at stock speeds with tight 4-4-4-12 timings and as high as about DDR-1960 at 8-8-8-15 by using the more exotic 2:1 divider. It appears our final limitation was the board/CPU combination and not the memory. We have no doubt the memory would have continued to scale well above 2GHz had there been additional FSB headroom to play with.

Memory Read - Command Rate 1N vs. 2N

In this analysis, intended to show the affect of 1N versus 2N Command Rate, we see that setting 1N (DRAM Command Rate to 1T) can improve synthetic memory read scores by as much as ~3.3% over 2N. Static Read Control Delay was held constant at 7 through the use of Ai Transaction Booster while both DDR3 memory frequency and timings were increased and Command Rate was forced to either 1N or 2N by BIOS.

We can conclude that DDR-1860, 8-8-8-15-CR1 is roughly the equivalent of DDR-1925, 8-8-8-15-CR2. This means modules that might not otherwise be able to reach the speeds necessary to provide the desired target bandwidth can take advantage of the performance enhancing capabilities of the MCH in order achieve this end. In most instances enabling Command Rate 1N did nothing to bring about early instability making this setting nothing more than free bandwidth for the taking. The source of the increased bandwidth comes from the addressing efficiency improvements that come with 1N commanding and the reduction in overall memory access latency.

450 FSB Quad-Core BIOS Settings Static Read Control Delay and Latency Considerations
Comments Locked

25 Comments

View All Comments

  • Owls - Tuesday, November 20, 2007 - link

    DDR2 is hardly "inferior". When comparing 4GB of DDR3 vs 4GB of DDR2, I can build a whole new computer with what I'd have spent on DDR3. It just doesn't make sense right now no matter how you cut it.. and only having 1GB of ram now?
  • TA152H - Tuesday, November 20, 2007 - link

    I run most of my machines with 512 MB, so 1 GB is hardly a problem.

    There are some things you need more memory than 1 GB for.

    When I see stuff like "It doesn't make sense no matter how you cut it", I instantly think you're an idiot. You're probably not, but that statement is absurd. There is always a group that the cost of the most expensive, and fastest parts, makes sense. The cost of memory is trivial compared to the cost of salaries, for example, and spending $500 to help someone work faster pays for itself very quickly.

    I think the main problem is that most people do not understand that more memory does not always make things faster. I deal with this all the time.
  • AnnihilatorX - Tuesday, November 20, 2007 - link

    Correct me if I am wrong

    The increase in FPS you see going from 400x9 to 465x9 is nearly 100% due to increase in CPU frequency

    The performance increase of a 465x9 RAM running at 2:1 memory divider would be less than 5% higher than a similar configuration of 465x9 with slower RAM running at lower divider ratios.

    That would mean there is no sense to buy a premium DDR3 for $500 extra for what you can do with less than 5% performance sacrifice with the dirt cheap DDR2 RAM.
  • snarfbot - Sunday, November 25, 2007 - link

    no everything you said is correct.

    the thing that really gets me though, is that pc6400 ddr2 is commonly capable of reaching 485mhz at lower timings. so whats so great about ddr3?

    on a p35 you can easily reach the same speed with cheap memory, at cas 5, sometimes even cas 4 with good overclockable ram.

    so basically the only benefit that ddr3 has going for it is the lower voltage required, and of course lower temps, not worth the premium. period.
  • Aivas47a - Tuesday, November 20, 2007 - link

    This is one of the best, detailed overclocking guides I've ever seen. Excellent job! I'm especially glad to have the mystery of Transaction Booster, Skew, and Clock Twister in the Asus bios explained.

    Now, if you guys could just prepare a guide for memory subtimings, the treatise would be complete. :)

    Thanks very much for this.

Log in

Don't have an account? Sign up now