The CDT and copywaza lab

[mrlobber]

Sick post KTE Can't wait the time I'll be able to run over everything you wrote and repeat it. I already noticed a couple of very slight differences with what I was doing but to see their possible impact, testing, testing, and again testing is needed

May I ask another question (seems to be trivial but maybe it isn't): which is your system partition? C:\ as usual (which would mean you have Superpi folder on your system partition), or maybe F:\, or even another one?

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.

From a pure theoretically speculative viewpoint , with every day it seems more to me that CDT itself is not about the memory/system cache balance at all, it is about those improvements you're talking about and the ultimate goal should be to find what kind of improvements these are and which are the actions creating them. The memory/system cache balance might be just an added bonus when doing together CDT + copywaza = (we know as) "CDT IV", that is, all the copying between drives / partitions is needed mostly for this reason (integration of copywaza into CDT).