How long should I run BurnInTest for?
Not an easy question. In our opinion, the chances or finding a problem in the first hour are relatively high, (the system gets hot, it’s the first run across the disk / CD and the first use of some of the drivers). Then every hour after that, the chance of finding a hardware problem drops significantly. The extra benefit of doing 12 hours compared to 6 hours is thus probably not great. Other nice technique is temperature cycling. All major manufacturers of electronic equipment do this, they have large ovens and fridges in which they test equipment. The expansion and contraction of components and solder joins brings to light many problems. You could do 6 hours On, 6 hours Off, then 6 hours On, to get some limited temperature variation like this. NASA and the Army load their equipment on to vibration machines, but this may be going too far for home / office use.
Related Questions
- I get "segmentation fault" error when I try and run BurnInTest Linux from the command line before any tests were started. What should I do next?
- BurnInTest does not have a test for my specialized hardware. Can I add my own test to be run with the other tests ?
- Can I run BurnInTest for Linux if I am booting my Linux distribution from a CD/DVD?
