Quote:
Originally posted by pHaestus
Make sure you give CPUBurn the right size cache and then set it to high priority. It executes extremely tight code that keeps CPU really really loaded. You can do the same thing with newer versions of Prime95 by setting it to smaller sized FFT lengths I think (though it isnt as effective). If you think about it DF is accessing the system RAM pretty heavily and also sometimes writing to the HDD. That means at least part of the time these are the bottleneck and keeping CPU from 100% true max load. With CPUBurn there's none of that 
|
Ok, I am now pretty sure I was using the wrong version of CPU Burn as the one I was using has only two options. #1 Run in error check mode (something like that), #2 run without error check mode. Nothing else. :shrug: