burn in?

[narayan]

what is burn in? why is it used? also, i am going to buy a k62 450 (after Christmas) should i o/c in small increments or can i just set it to where i want it? and while I'm in the Christmas spirit, thanks to all for the helpful replies since i've been here. and how do i make the smiley faces in my messages?

[Wiz]

let the computer run for a little while before O/Cing, maybe a week or 2. then overclock in small increments.

[Chainsaw]

smiley faces? http://www.sysopt.com/forum/faq.html#smilies

........CHNsaw http://www.sysopt.com/forum/biggrin.gif

[This message has been edited by Chainsaw (edited 12-09-1999).]

[narayan]

what is the purpose of small increments? i do not understand why this is important. http://www.sysopt.com/forum/smile.gif smiley faces rule

[This message has been edited by narayan (edited 12-09-1999).]

[scotter]

it's like breaking in the motor in a car if you take it out and red line the **** out if it from the start 99% of the time your going to blow it up. but if you break it in over a few weeks then you can red line the **** out of it with out to much worry. Get it http://www.sysopt.com/forum/wink.gif

[Chainsaw]

narayan,
My understanding of "burn-in" is the testing and observation of how a piece of equipment or combination of equipment performs under extreme conditions.
The reasoning behind using small increments is to gradually step up to finding the point where the equipment is performing to it's maximum capacity. If you do this gradually, you are able to determine at exactlly which point the performance begins to deteriorate or even fail ie. the dreaded "blue screen of death" or other indicators of performance loss. Once you find this point, you can take a step back until your system is stable again, or add measures such as increased cooling to stablize your system at that point.
If you were to just jump to a greater clock speed or higher multiplier all at once, you loose the ability to determine that precice point at which your system (every system is a little different) will best perform.

Best of luck in all,
and don't forget to keep 'er cool,
........CHNsaw

[narayan]

scotter and chnsaw, makes sense. so is there a "break in" period, or is it an experament until u reach the limit?

[narayan]

scotter and chnsaw, makes sense. so is there a "break in" period, or is it an experament until u reach the limit?

[Chainsaw]

narayan,
You ask an very interesting question, but I doubt that you will get any single answer to it. I think that "burn-in" is a loosely used term and is interpreted in different ways. I plan to watch this thread closely to see the answers you will get to this question. I'd be interested in hearing how a hardware engineer involved in chip design might use the term.
........CHNsaw http://www.sysopt.com/forum/wink.gif


[This message has been edited by Chainsaw (edited 12-09-1999).]

[scotter]

I think most people run it for a few days to a week at any setting befor making the next jump, it all depends on how your using your system
there are a few programs that will help (burn) your system in as in doing RC5 cracking, or running seti@home, looping quake2 time demo's etc, etc, over night. If you wake up in the morning and your system's still doing it's thing you can almost call it good http://www.sysopt.com/forum/smile.gif
But I would not just clock it,then start up a program like that and go to bed you need to make sure your temp's are ok and the thing is stable for a while first http://www.sysopt.com/forum/smile.gif

Anyway that's my take on the whole thing http://www.sysopt.com/forum/smile.gif

have fun and keep it cool http://www.sysopt.com/forum/smile.gif