Quote Originally Posted by kink View Post
I doubt the usefulness of this method. wPrime simply starts one thread per core and probably sets the affinity mask so that each thread runs only on one dedicated core. The problem is that there are always loads of other threads running (other applications, services, OS itself), which are scheduled to execute on some available core; another active thread may therefore interrupt the second wPrime thread, then the 4th one, afterwards the 1st one etc. There has been quite a change to the thread scheduler in Win7, so this whole thing additionally depends upon your OS too. I did a 1024M test on Win7 and the order wasn't stable at all, no surprise there...
kink: I agree with you on 99% of what you said, I don't doubt all the references to Affinity, services, apps, OS and interupts...
Which is why I mentioned all the variables...

No matter how much you tweak ACC using this method your NEVER going to get a perfect sequence run using WPrime or P95 for that matter!

The 1% I dissagree with you on is the usefulness of this method...
Although you'll never get it perfect, keeping things closer to inline has helped me settle things down a number of times.

I just thought I would throw it out there, if people find it usefull, great, if not, it seems to work for me... So I'll keep using it...

It is what it is...