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 :-)

As we speak we are now testing 1.43 with AMD users. (and making good progress)
Seti AMD users
That with the automatically detect on BOINC task is a good idea. Will surely add it.
Making the name shorter helps sometimes putting in Einstein will throttle any Einstein task stating with this name.

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.

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

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

New version that does all that. Download 1.45

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.

Indeed TThrottle does affect all project on any core.
The main problem is that the OS distributes work over the cores. And not only at the beginning and end of a task. throttling all projects should give a more or less equal distribution of work. But as not all work is equal... Some work may increase the temp more then others. And the reading may not be too precise. Intel e.g. gives a 1C tolerance and the converter may be 1C off as well. That could mean if you see a 4C difference in core temp it may be still be within normal tolerance. Meaning what you see is not what happens and the cores may have exactly the same temperature. If there are enough request I may add a feature to limit throttling to specific project only, if that is what you mean.

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.

The changes involve running the 32 bit version on a 64 bit system and redirecting the user with a warning. Made the 1e program tab simpler by removing most of the unused buttons etc and placed an expert check for those who want it anyway. Makes some room for the list. Most early users can now (normally) remove all programs from the 1e program tab, by selecting and "remove". Fixed the BOINC detection in the X64 version. And added additional AMD processor info.

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.

Try 1.51, I made some memory changes as well.

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

Could be a number of things. Did you disable the virus scanner from the boinc data directory? Are there any other program communicating with BOINC a FireFox app?

I get reports back that the memory problem is solved in V 1.54. There is a V 1.55 for testing with some improvements in the GPU throttle for laptops.
Thanks to Sekerob, Mikael and Alain for the testing.

Hi Fred, 1.53 is still doing fine. On Vista Quad it has trouble reading the system data only showing 1 core temp and 1 gpu temp, and not doing anything, certainly not graphing, trying all sorts for version 1.54 and 1.55. Tried both admin and user lever installs.cheers

PM me the log data so I can see what is going on.

A new Version 1.56 is released.

A lot of user request are in this new release.
For AMD users the 0x10 Family problems seems to be solved thanks to Thierry, who send met the log file.

For the upcoming version: a French and Dutch release is planned.
I'm still looking for other languages, please sign on.
And if there is an native English reader, who can check my English for style errors etc.