Folding program is ignoring my idle cpu...
Posted: Mon Apr 14, 2014 8:06 pm
Hello...new user/donator here. I have a new HP Envy win 8.1 laptop with a whippy intel i7 4700MQ processor. Figured I wasn't working this enough playing spider solitaire and checking emails, so Downloaded the Fold program yesterday and ran my first work unit.
Being a new laptop and not ready to come even close to breaking it, was concerned to see (with use of the Open Hardware Monitor program mentioned in a prior post) that the core temps were being stepped up with increased speed and frequently hitting 99C. (People around me notice the increased fan noise.) That's pushing the limits too close from my standpoint. I have the slider at minimum. Haven't played with the cpu slot number as I do not understand what I'm doing.
So, being an old mainframe tech and familiar with the idea of prioritizing programs so that some got more processor time than others, switched to "run only when idle" button, thinking that ....OK, the proc is idle, so some work from the WU will slip in here and get processed.
Well, apparently it does not. Just sits there. The program never wakes up to the fact that there is plenty idle time (the four cores averaging 1%). Even let it sit overnight with all other programs closed...and no progress was made on my second work unit (the first, even with me playing around with it some, got done in about four hours).
So, I'd feel more comfortable seeing the temps stay below 80C. From what I've read on the forum so far this is going to be difficult considering the inherent quirks of processor engineering and program design.
But did I miss some adjustment? Or something to wake the program up when it waits for idle?
Being a new laptop and not ready to come even close to breaking it, was concerned to see (with use of the Open Hardware Monitor program mentioned in a prior post) that the core temps were being stepped up with increased speed and frequently hitting 99C. (People around me notice the increased fan noise.) That's pushing the limits too close from my standpoint. I have the slider at minimum. Haven't played with the cpu slot number as I do not understand what I'm doing.
So, being an old mainframe tech and familiar with the idea of prioritizing programs so that some got more processor time than others, switched to "run only when idle" button, thinking that ....OK, the proc is idle, so some work from the WU will slip in here and get processed.
Well, apparently it does not. Just sits there. The program never wakes up to the fact that there is plenty idle time (the four cores averaging 1%). Even let it sit overnight with all other programs closed...and no progress was made on my second work unit (the first, even with me playing around with it some, got done in about four hours).
So, I'd feel more comfortable seeing the temps stay below 80C. From what I've read on the forum so far this is going to be difficult considering the inherent quirks of processor engineering and program design.
But did I miss some adjustment? Or something to wake the program up when it waits for idle?