Do people still do that? Used to be common practice to power on equipment and let it sit, either idle or full-tilt, for a couple days before even starting to configure it. Let the factory bugs scatter out.
Yeah, we did that at my last company to make sure our hardware was up to spec. We deployed an IOT device for long term outdoor installations, so it needed to survive very hot temps. We had a refrigerator we gutted and added heat to, and we’d run a simulation with heavier than expected load for a couple days and tossed/RMAd the bad units.
That was a literal burn in, but the same concept ak applies to pretty much everything. If you build/buy a PC, test the hardware (prime95 CPU test, memtest for RAM, etc). Put it through its paces to work out the major bugs before relying on it so you don’t have to RMA a production system.
Probably performs a good burn-in for them too.
Do people still do that? Used to be common practice to power on equipment and let it sit, either idle or full-tilt, for a couple days before even starting to configure it. Let the factory bugs scatter out.
Never heard of that, interesting
https://en.m.wikipedia.org/wiki/Burn-in
Yeah, we did that at my last company to make sure our hardware was up to spec. We deployed an IOT device for long term outdoor installations, so it needed to survive very hot temps. We had a refrigerator we gutted and added heat to, and we’d run a simulation with heavier than expected load for a couple days and tossed/RMAd the bad units.
That was a literal burn in, but the same concept ak applies to pretty much everything. If you build/buy a PC, test the hardware (prime95 CPU test, memtest for RAM, etc). Put it through its paces to work out the major bugs before relying on it so you don’t have to RMA a production system.
I do; I use a four pass destructive run of badblocks on new drives before implementing them.