Quote Originally Posted by mrlobber View Post
KTE, you did that again That 5sec difference is all I'm looking for. Will try to replicate your runs as soon as I can... although Asus boards mostly are faster clock-for-clock than Gigabyte (and I wonder, could that make a difference somewhere in CDT as well?)
I had a chance of getting P5K Black Pearl twice but I turned it down in favor of higher FSB on this board (usually). But it seems my CPU is walled at 480FSB so P5K would've been better for "absolute" Pi times. I wish I would've know that earlier.
Just to 100% clarify the things how we are doing those 30% CDT , could you write the CDT copy sequence you are doing step-by-step, including the paths involved, whether any pauses between the copying of the files and literally everything you're doing while applying the information we've got about CDT
*I chose the hardware/OS settings I have already talked about at bootup in BIOS and in the previous Windows session.
*Boot up.
*Opened Task Manager to check memory/cache.

-My SPi folder is Drive C: which is the 1st partition on one SATA drive.
-My second folder is C:\CDT which is on the 1st partition of the same SATA drive.
-My third place of movement is Drive F: which is 1st partition on another SATA drive.

-Two identical SATA II drives.

**(On them runs) I started SPi, in Task Manager set the process priority of superpi to "Real-Time".
**I then ran 16k three times, 128k once, 1M twice, 32M upto 6th loop once and then choose 32M until the final window prompt to start it appears. I do nothing further with it yet.

Additional Info: I don't use the mouse (I/O). In case you don't know, I/O takes up CPU consumption, that's why they say "don't move the mouse during a bench". It will lower your scores. Moving the mouse fast does this worst. If you've captured screens/saved CPUZ validation files at very unstable clocks, you will know this very well. You move the mouse as slow as possible (don't take years please, it won't help ) and smoothly to where you need and leave it there.
I use Alt and scroll keyboard keys and hit the Enter key very fast 3 times successively for my runs. It DOES make a difference many times.... with me anyway.

What I did for the above CDT runs?

Step 1:

1: I opened Windows Explorer (folder side view) and right-clicked a 632MBx3 (1.85GB) RAR file which I have already made and left in location Drive C:\ called CDT.RAR.
2: I choose "Copy" and then right-click location Drive F:\ in the left hand-side folder view and choose "Paste".
3: I wait until it finishes copying. As soon as it finishes (no delay) I repeat the above two steps twice more for a total of 3 times file moving, rewriting over the previous file each time.

Step 2:

1: I then right-click the CDT.RAR file in Drive C:\ again and choose "Copy".
2: Then I right-click folder C:\CDT and choose "Paste".
3: I wait until it finishes copying. As soon as it finishes (no delay) I repeat the above two steps twice more for a total of 3 times file moving to this place, rewriting over the previous file each time.

Step 3:

1: I click on Drive F: and right-click the same folder CDT.RAR in it, and chose "Copy".
2: I right-click Drive C: and choose "Paste".
3: I wait until it finishes copying. As soon as it finishes (no delay) I repeat the above two steps twice more for a total of 3 times file moving to this place, rewriting over the previous file each time.
4: on the last copying over, I initiate the copying and close Windows Explorer.

Final Step:

1: I look at the Task Manager to see when the memory value reaches its max before starting to drop -> most of the time this takes 10-15 seconds delay with my experience.
2: As soon as I see it losing memory, I close Task Manager and wait 5 seconds more.
3: I then hit Enter and let 32M start.

Then... if it turns out a slow run, you sit back and cry "Why me!" ... LOL!

Are you sure you didn't swap these numbers? I mean, 550/553 for CDT and 535/550 for CW...
Nope. CW gave me bigger memory/cache but while that DOES improve times very much from stock, it isn't the same thing as CDT -> based on my experience.

CW is the best SPi method of improvement that I knew before this=> there is NO way I can get CW times out of my hardware/setup without running CW=> practically impossible as all I do is hit keys. This is the same for many people that I know including most of you dear geeked out readers.

From what I've experimented with over 4-5 methods of improving memory/cache and getting it to from 580-490/620-500, improving memory/system cache is not all that is happening here with CDT. That's what CW does best.
CDT is improving the memory/cache like CW but also there is something do with the method => something happens to your hardware/OS prefetch/cache by running this method which you do not get by running CW or anything other that I've tried and it is this that improves the time over a CW.

Also a few more personal comments into understanding this based on the above notes:

I don't know anyone who understand computers completely, not even Intel or AMD. Ask the lab engineers when they design a core if its always like they expected-> never.

You can run ANY tweak and get better times at the same setting for everything compared to your own PB. This is because on a different day and time the OS can behave and prioritize slightly more efficiently, and this "sightly" can easily make a second of a difference over a 13 minute bench. Run SPi on Linux and you'll see how its quicker, meaning the way the OS behaves matters crucially.

Some hardware is quicker than others at the same settings. This is beyond our user control.

You can run a CDT perfectly according to the procedure Elmor/OPB/I or anyone does but still not see any gain over CW. I've had this happen to me... but out of the blue, by that I mean beyond your control or understanding you may run it once more time and it will give you a faster time than whats possible otherwise with CW. All you do is, sit back and smile and know that it was a more efficient run, like you would say about a better CW.

My last runs were quite unfair. I did CW 4 times, and the two best times you see there. But I did CDT only once. Mainly because I didn't want to install GFX and so on again if it crashed and it takes so long. FWIW doing CDT is very hard on RAM, I noticed when I had looped 32M perfectly at higher clocks/lower timings with CW, but when I tried doing it after CDT, it failed repeatedly on the first loop on those settings, and even at stock clocks after CDT: (link place reserved because I can't access the drive yet)

Not even Orthos or OCCT caught those errors for over 2 hours, only Memtest, P95 and CDT-32M did. So now its become my way of memory stability testing too.

CDT leaves an "aftermath" effect of your system. Your times improve not just right after the method but maybe for all of the day while you have the system running. I've seen this with all 3 of my tests, on Celeron D, Pentium 4 and Core 2.

I kind of wish I had better hardware now, then I could really test CDT by running the same clocks/latencies as others who fail to understand or believe, but I did this on purpose. Getting better hardware was quite easy for me, although time and interest is an issue. People asked for "C2D" and so I tested one, but my testing hasn't ended yet, its preliminary. In one major way it is good not to have done it because that would end up with users here behaving the same way as what they do with OPB, which would make you see the "not-so-polite" side of me where I'm as sour as any of you can be and I don't want to be banned for no fault of mine. Wherever you have "lobbies" that always happens, and in this case it would be those who have ran SuperPi day and night more than the seconds I've used a computer for lobbying saying "they know better". I had a Duron earlier this year that was giving wrong readings and high benches of 4GHz+ and the daft of the onliner visitors reacted the same petty way, regardless of me saying "theres definitely something wrong". This is where this emoticon is best used =>

BTW, I'll decrease that CDT time further yet, how much I'm not sure, maybe even only a ms but I can drop it a little more at those settings I feel.