Kreij bro...
It must have been a typo...I know u get the right info...But I think WCG uses only idle cpu cycles
Correct me if Im wrong!!
You are right Dusty, what I meant was that your IT department is correct in that it will use CPU cycles that would not normally be used in your day-to-day computer usage (ie. the idle time) This is, however, completely a non-sequitor answer on their part as anything that you do that is not in the normal course of your daily routine on your computer, will use more CPU cycles. So if you launch a work related application more than usual on a given day, you will be using more CPU cycles!!! OH THE HUMANITY!!!
That is why I added (Duh) after the comment. Anything you do on the computer uses CPU Cycles.
So we can play at their game ..
Guys!! The reason that we run WCG on the computer when they are idle is that even in solid state circuits, you still have the basic PN junction for each transistor switching component layed out on the die. When a PN junction is left idle for too long, the charge threshhold float balance (CTFB) starts to swing toward the stronger of the two (which is always present as the junction characteristics are determined by the physical properties of the die). This means that when the processor is left to idle for extended periods of time, the likelyhood of PN junction freeze (producing switching errors) grows exponentially, and will result in premature processor failure. The only way to ensure this does not happen is to keep the junctions in a continuously transitioning state. The only reliable way of doing this is by making sure the processor does not enter the idle state too often, which is exactly what the WCG software does. We are just trying to make the company's computers more reliable and a better investment overall.
Think outside the box ... WAY outside the box.
... and remember, if you can't dazzle them with brilliance, baffle them with bullshit.