Burn in cpu??

[vheff]

Hi,

If I've got some time on my hands prior to going live in a production environment, I've heard that it might be a good idea to burn in my cpu? I've seen some posts on memory burn-ins, but not CPU.

Has anyone done this, or is it a waste of time?

I noticed that the ESX Performance Tips PDF recommends testing the memory for 72 hours, but nothing on testing the CPU?

Message was edited by:

l9nux

[esiebert7625]

I've been working with servers for many years and have never burned one in and I've never had a problem because of it. Electronic components are not like mechanical ones and do not really need to wear in initially like a car engine. Obviously it can't hurt to do this and if you want to do this prior to using them an easy way is to create some VM's and run the cpubusy vbs script on the VM's to give the CPU's a real workout.

http://www.vmware.com/community/thread.jspa?messageID=493849

http://www.vmware.com/community/thread.jspa?threadID=69616&tstart=330

fyi...if you find this post helpful, please award points using the Helpful/Correct buttons....thanks

[bigvee]

The reason most people recommend a burn in is to try to identify problems prior to the server going into production. Most issues Ive seen pop up in hardware running ESX is memory related which is why most recommend a good burnin to ensure everything is up to snuff.

If you have some spare time I recommend it, chances are it wont find anything but if it does you'll be glad it happened when nothing was on it.

Just my 2 cents.

[petedr]

We usually let our servers burn for a day or two especially if there are internal harddrives, always a good idea to burn in. As for CPU specifically it can't hurt especially if you have the time to do it.