Madshrimps News and interesting articles and howtos from the Web!Articles and Reviews, CPU Coolers, Cases, Motherboards, Videocards and more...Howto and guides on Modding and Optimising your PCFollow Interesting Discussions at our Forums!Find out more About Madshrimps and its crewStatistics - What article/howto is most popular and more!
[M]adness
HWFaq Hardware and Software Frequently Asked Questions - HWFaq
Contests Win Hardware! Join our contests now!
Search
Links
Sponsors
Send News
Video Card Comparison Charts

Intel Core i7 In-Depth Performance Scaling Analysis

Aircooled Heatsink Reviews

35x 120mm Fans Tested

Sponsors
.Priorweb
Arctic Silver
Asus
Caseking
CoolerMaster
Danger Den
Dollarshops
Geeks.com
Gigabyte
MSI
OCZ
PC-Cooling
Scythe
Swiftech
Tones
||-More-||
 
 
Stabilizing your memory overclock on Core i7 platform - Back-to-Back Cas Delay Investigated
Stabilizing your memory overclock on Core i7 platform - Back-to-Back Cas Delay Investigated
In today´s short article, we´ll have a look at the effect of just one memory timing, the Back-to-Back Cas Delay timing, which seems to be one of the more important timings both performance and stability-wise. If you´re looking for a solution for your high-frequency capable memory kit, performance increase with low-frequency memory or stabilizing high BCLK/high memory ... this is something for you.
Author massman
Editor jmke
Date 2009-06-30
Discuss 6 comment(s)
Print this Article

 
 


  Introduction

It has been a while since my latest article for which I blame examinations at school and of course the Gigabyte Open Overclocking Competition, which eventually led me to the great city of Taipei. However, since I have a few weeks of vacation now, I'm able to present you some of the findings of the Madshrimps team regarding the Core i7 platform.

Maybe you remember the X58 motherboard round-up which was published already four months ago, close to the release of the Core i7 platform. Having 7+ X58 motherboards at home (I was sent a couple more after the round-up) gave me, and my collegues, the opportunity to digg deeper into the different aspects of overclocking an i7 processor. In fact, we focussed on three different aspects:

  • BCLK frequency
  • Memory frequency
  • The combination of BCLK and memory frequency

    As for this article, we'll be spending time on one setting that seems to give us the best solution when running into either stability or performance problems when overclocking the memory. It seems to be one of the key elements to stabilize the memory when running at high frequencies.

    Back-to-Back Cas Delay

    Madshrimps (c)


    This one setting I'm talking about is a memory timing called "Back-to-Back Cas Delay" (referred to as B2B in the article). To explain you why this particular timing is so interesting, I need to tell you the story of how we figured out all this, since it's vital to the understanding of it's impact on stability. First of all, this timing seems to be available on Asus motherboards only. Why? We don't know, but on the Asus motherboards it defaults at "0" when set to auto in the bios. But, before we digg in deeper: the background story.

    To start with, I have to explain a concept named "low-clock challenges", which is mainly used within the enthousiast community to work out a software/hardware configuration as efficient as possible. Basicly, you limit the maximum frequency of the cpu and then try to get a score as good as possible using a certain benchmark, in this case 32M. This allows the overclockers to compare their tweaking skills and, if necessary, figure out hardware-related performance problems.

    Now, when tweaked properly, a 4GHz Core i7 combined with 1GHz CL7 (2000CL7) memory will give you a time around 8 minutes 50 seconds (in the 32M benchmark). However, certain people seem to be able to run at least 10 seconds faster, which could not be explained by software tweaks solely. To keep the story short: it occured to me that almost all fast configurations were Asus-equipped.

    On the Madshrimps forums, I wrote quite a lenghty post regarding my performance issues in the 32M low-clock challenge. At initial stages, I believed the hardware prefetcher options in the bios were causing this since the Asus motherboards were the only motherboards that had them available in the bios. However, after testing both the Rampage II Gene and Foxconn Bloodrage (new bios has prefetcher option) I know that those two prefetchers are not the cause. I presume the best way to read that post is just for understanding that there's a significant difference in clock-per-clock performance between certain motherboards.
    (Link: 32M and i7, a motherboard's choice?)

    The second part of the story is actually located in another thread, but since the information is spread over numerous forums, I'll give you the details in short. Basicly, Jody (3oh6, hardwarecanucks.com) and I were testing the Rampage II Gene at the same time and both our motherboards were incapable of running an Elpida-based memory kit over 930MHz, no matter what voltage or cas latency. After a few hours (okay, 10+) I found a reasonably stable configuration when playing with the Back-to-back Cas Delay timming. There are a couple of weird issues with this timing, though.

    1) The instability caused by this timing doesn't scale as you'd expect. It's equally unstable set at "0" as it is set at "10" whereas you'd expect it to be more unstable at a lower value.
    2) The instability itself is not typical for memory instability: instead of getting a BSOD or a reboot, the system just locks up.
    3) The instability seems to be very particular to certain benchmarks. I am perfectly capable of running Superpi 2M as much as I want and even copying large files doesn't cause the system to lock up, but after 2 seconds of Superpi 4M the system hangs.
    4) In dual channel configuration, there's absolutely no issue whatsoever with this timing: this value set at "0" is perfectly stable
    5) The issue cannot be solved by increasing the voltage or loosening the timings. The setting "10" is as unstable at 1.8v Vdimm and 1.6v Vqpi/dram as it is at 1.65/1.50v


    A fellow overclocker has tested the influence of this timing on the performance in 32M and changing this value from 0 to 12 has a negative effect on the performance as follows: at loop 4, the benchmark is already 1 second slower. Taking into account that the benchmark has 24 loops in total, that would mean that changing this timing will cause you to lose about 6 seconds, maybe 7. And, coincidence or not, this is almost exactly what I'm losing in comparison to the best scores. This "finding" also occurs on other motherboards; initially I was using the DFI Lanparty DK X58-T3eH6 for testing purposes and again I had times around 8 minutes 50s. But, this board gives me perfect 200/2000 stability out of the box ... so I assume the back-to-back cas delay timing has been set to 12 by default on this motherboard to maximize stability.

    In short: the Back-to-Back Cas Delay timing has a significant effect on the stability of you memory overclock, but seems to have an effect on the performance as well. On the next page, we tried to find out how much effect the timing has on the performance.

    | Next ->>




    Quick Page Jump:

    More reviews in this category can be found below:

  • MSI GTX 275 Lightning Shatters World Records on LN2
  • Leadtek Geforce GT 220 Extreme Overclocking Experiment
  • Intel Core i7 In-Depth Performance Scaling Analysis
  • Stabilizing your memory overclock on Core i7 platform - Back-to-Back Cas Delay Investigated
  • Galaxy Geforce 9500 GT Voltage Modification and Overclocking
  • AMD Phenom II In-Depth Performance Scaling Analysis
  • Madshrimps takes the AMD Pifast world record
  • AMD Phenom II X4 940 Subzero Overclocking Test: 6Ghz Obtainable?
  • AMD Phenom In-Depth Performance Scaling Analysis
  • Twintech 9600 GT Overclocked With Phase-Change Cooling
  •  
     


    Copyright © 2001-2010 Madshrimps / JMkeOC.com, All rights reserved.
    Graphical Design by Dennis Kestelle, Programming by John Meys, Paul Meys and Frederik Colardyn, Overall Site design by John Meys

    All information and graphics contained in Madshrimps are sole property of the Madshrimps crew and may not be reproduced or copied in any manner without written permission from us.

    BTW-BE 0888919678

    ADS by G
     
     
     
     

    Search Madshrimps
     
     
    Google
    Search Madshrimps:

     
     

    Daily News
     
      Hardware TPM Hacked...
    Chinese Site Copies...
    Configure Your Comp...
    Seagate debuts the ...
    AMD to Sample 32 nm...
    NVIDIA Optimus - Tr...
    Windows 7 Battery N...
    Asus jumps the gun,...
    MSI Shows Passive C...
    AMD's ATI Radeon HD...
    Intel's Sandy Bridg...
    Intel Core i7 660UM...
    AMD reveals Fusion ...
    MSI P55-GD55: A Mai...
    AMD Reveals More Ll...
    AMD’s Radeon HD 557...
    Gigabyte HD 5670 OC...
    Sapphire HD 5570 1 ...
    Powercolor HD 5870 ...
    [M] MSI P55-GD80 en...

    Syndicate Madshrimps Daily News with our XML/RSS Feed!

    Receive updates by e-mail

    Read more News...
     
     

    Sponsor Space:
     
     
     
     

    New Content
     
      Articles/Reviews:
    USB 3.0 and SATA 6G...
    MSI Wind U135 Revie...
    Intel Clarkdale CPU...
    Three AMD 785G Moth...
    Vidabox Premium Wir...
    OCZ Throttle 32Gb e...
    Seven Intel P55 Mot...
    RAID 0 Stripe Sizes...
    Gigabyte Geforce GT...
    Intel Clarkdale vs ...
    Swiftech Apogee XT ...
    LanCool PC-K58 ATX ...
    Larkooler Universal...
    MSI GTX 275 Lightni...
    MSI Geforce GTX 275...

    Howto and Guides:
    Building a 300W Fan...
    NVIDIA Geforce 8400...
    NVIDIA Geforce 8800...
    Reviving and Volt M...
    Protect the core of...