I made a program that monitors the Processor core temperature and throttles a running task so that the temperature stays within limits. It works on Windows 32 Bit Intel only. But if there are AMD users around who want to help… Processor needs to have a build in sensor and cpu register, so most computers up to 2 years ago will work. I made this specifically for my laptop.Download
This is a beta program, but tested on several computers (XP/VISTA). Suggestions welcome.

AMD users: I'm looking for testers. Even if this message is old please contact me.
A new version 1.1 with automatic program detection is ready for download.

A new version 1.4 is available.
You can make a graph of the temperature.For 1 or all processor cores.
This allows monitoring from minutes to the whole day.
Download this free program

Although I've responded to Fred per PM a few days ago, I've decided to write my comments also here, to stimulate development :-)

• V1.4 immediately crashes on 600 MHz AMD Duron. I admit my CPU lacks "a build in sensor and cpu register", but still, it should not behave that harsh to the old uncle ;-) (Fred is already looking into detecting and using AMD regs correctly.)
  
• On my C2D T7200 it works as advertised. I appreciate the large temperature graphs, I was looking for ages for something like this!
  
• I think that especially multiproject BOINC crunchers would appreciate a possibility to enter not just single executables (which get occasionally replaced and renamed), but whole path roots, like ...\BOINC\projects\ or ...\BOINC\slots\, otherwise each "new" application will not get throttled.
  
• Beware! At least the TThrottle 1.4 incorrectly shows its name as "TTrottle", which is nearly similar to a german swear-word :-)
  

Peter

Although I've responded to Fred per PM a few days ago, I've decided to write my comments also here, to stimulate development :-)

Hi, very cool program - if you get the joke - !!

Really it looks very professional and hopefully it will help with my automatic shut off problems.

I was wandering if something could be done to make it easier (i.e. foolproof and let's say automatic) to detect the processes it monitors and regulates: many of the applications running on boinc are frequently updated and this makes it necessary to go and update the list. Plus, many boinc users like to run a variety of projects, so this makes it a long task to load them all in TT.

This is just a couple of thoughts to beef up the wishlist, I am sure you are already working on it.

Speaking of wishlist, it may almost be a good idea to implement your program IN BOINC, or otherwise work on connecting the two programs some more.

Keep up the good work!!!

I was wandering if something could be done to make it easier (i.e. foolproof and let's say automatic) to detect the processes it monitors and regulates: many of the applications running on boinc are frequently updated and this makes it necessary to go and update the list. Plus, many boinc users like to run a variety of projects, so this makes it a long task to load them all in TT.

Speaking of wishlist, it may almost be a good idea to implement your program IN BOINC, or otherwise work on connecting the two programs some more.

I was wandering if something could be done to make it easier (i.e. foolproof and let's say automatic) to detect the processes it monitors and regulates: many of the applications running on boinc are frequently updated and this makes it necessary to go and update the list. Plus, many boinc users like to run a variety of projects, so this makes it a long task to load them all in TT.

This would be exactly covered by automatically regulating each and any application, running under the BOINCprojects path tree. Maybe in this case it would be good to implement exceptions from such automatism?

Speaking of wishlist, it may almost be a good idea to implement your program IN BOINC, or otherwise work on connecting the two programs some more.

Exactly

Peter

A new version that includes 64Bit support (tested on XP64 / 2003) download v 1.47

Hi,

you guys are doing a great job, the program seems to be making good progress!

One thing I was wondering now, is:

Is there some sort of rule of thumb to mantain a reasonably efficient run time in terms of FLOPS per Kilowatt hour?

Any way to set let's say a maximum core temperature in order to maximize computation with the least power consumption? Or are they simply directly proportional (so if i double run time, computation ouput will grow twice as much and so will be consumption)

I am not sure I am making myself clear, or that I am making any sense at all!

Please tell me if this has been covered elsewhere. In this times of greater concern for the environment, I feel BOINC should take into account that an effort to reduce consumption may look attractive to potential crunchers that have ecologic (and -nomic) worries.

Thanks

Been running it for past 48 hours on a quad. It seems the throttling is across the board rather than core specific...am I right? At least when running a combo of WCG Rice and D@H and watching in Process Explorer it's torquing off all 4 processes. I know D@H is the one raising temps about 4C as does Primergrid and QMC, so controlling at core level would seem a way to keep other sciences unperturbed.

For the graph, would be nice to see which science is using what core.

Thanks for the excellent addition of tools to optimize crunching.

PS: I'm using ThreadMaster GUI to set a percent per science during summer, but temperature controlled use at science level would I think be the better solution for many and use maximum CPU still as the ambient temperature fluctuates.
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

Been running it for past 48 hours on a quad. It seems the throttling is across the board rather than core specific...am I right? At least when running a combo of WCG Rice and D@H and watching in Process Explorer it's torquing off all 4 processes. I know D@H is the one raising temps about 4C as does Primergrid and QMC, so controlling at core level would seem a way to keep other sciences unperturbed.

For the graph, would be nice to see which science is using what core.

Thanks for the excellent addition of tools to optimize crunching.

PS: I'm using ThreadMaster GUI to set a percent per science during summer, but temperature controlled use at science level would I think be the better solution for many and use maximum CPU still as the ambient temperature fluctuates.

There's already a science exclude option, but then the throttling would only work if the specific "hot" were running when the objective is to maintain a maximum applying to all cores whilst even in summer the RICE would cause the CPU to get too hot at 100% load unless setting Speedfan to cause the curtains to wave.

As to tolerance, been playing with Process Lasso to quickly move affinities and temps very closely follow the core where D@H is running on. Apps as CoreTemp and Speedfan show same, so I'm reasonably confident that the temps are well represented, much closer than Intel is saying.

Anyway, just a thought to make the control science specific. On a Quad easily 5-10% of computing power is lost because of a very hot running science. ThreadMaster still allows to reign in the hottest individually, but TThrottle would be the ideal all-in-one control, set and forget 365 day of the year.

cheers

Added: Other thought, considering the tolerance, running the control on a composite temp of all cores might be a way instead of the absolute measured for any core, but that would only be a minimal gain I think.
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

I am using the beta (1.4.7) version.
I now have a functioning throttel.
Boinc info is now shown.
I can now run BOINC tasks unattended.
THANK GOD!

I tried both ReadyDriverPlus
and Driver Signature Enforcement Overrider 1.2
from http://www.ngohq.com/home.php?page=dseo

Both work but I settled with Overrider.


system is:
ASUS M2N-SLI Deluxe
AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Microsoft® Windows Vista Home Premium 64

Changed this AM to the latest beta (1.4.8) version.

I stopped using Driver Signature Enforcement Overrider 1.2 yesterday because of failure to stay in test status.
I went back to ReadyDriverPlus and it is still working.
I see no real difference except it now shows milkyway.cs.rpi.edu_milkyway in the BOINC list.

Fred: ... do want a current log?

Thanks again
____________
--
benDan

Changed this AM to the latest beta (1.4.8) version.
I see no real difference except it now shows milkyway.cs.rpi.edu_milkyway in the BOINC list.

New version 1.51: Allows monitoring GPU (CUDA) temperature. A separate throttle can keep the GPU temperature at the set temperature.
The graph shows the temperature drop as one task ends and another task is starting. Another interesting thing came up. The cpu tasks that communicates with the GPU needs to run at about 70% of time to fully fill up the GPU with work.

Fred,

Running 1.47 for longer have had several times a "Quota 100 reached ..." type of system instability. Launching, saving data, became impossible. Killing TThrottle restored system stability.
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

Fred,Running 1.47 for longer have had several times a "Quota 100 reached ..." type of system instability. Launching, saving data, became impossible. Killing TThrottle restored system stability.

Hi Fred,

Gave 1.51 a spin and after 4 hours, the Firefox app with 3 longer writings, not yet saved, disappeared off screen. Trying to relaunch gave the same relaunch error... Quota all used, free resources... Again when ending TThrottle, the temp icon (coretemp), went from 100, which I think is the junction point, to the regular op temp.

Thanks
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt