Hi again,
Is there any issue running all the standard tests at 100% utilization (ie, CPU@100%, RAM@100%, 2D@100%, etc)? Is this not recommended for general production line type burn in scenarios? If no, why not? Are there any types of known failures we should expect in that scenario? What kinds of considerations should be made when deciding how hard to run all the tests?
(FYI, I am using the newest BIT Pro for both x86 and x64 and also got that packet error issue another poster recently pointed out when running the test as a loopback at 100%)
Thanks!
-S
Is there any issue running all the standard tests at 100% utilization (ie, CPU@100%, RAM@100%, 2D@100%, etc)? Is this not recommended for general production line type burn in scenarios? If no, why not? Are there any types of known failures we should expect in that scenario? What kinds of considerations should be made when deciding how hard to run all the tests?
(FYI, I am using the newest BIT Pro for both x86 and x64 and also got that packet error issue another poster recently pointed out when running the test as a loopback at 100%)
Thanks!
-S
Comment