Topics

I started this project when I got really annoyed with BOINC manager, not able to cope with the 1000+ WU. Frequent waiting messages, incredibly slow and lost connections.
And connecting to remote computers in the BOINC Manager, is not very sophisticated.

So my goal was to make something that works on my computers. And.... it is probably useful for others as well. So the project got out of hand and is taking up more time than anticipated.

First I started out with one window per computer, as this is the fastest approach and that works well.

As suggested by my earliest tester and great help Corsair, I started combining everything into one Window and that was a good idea. It gives a better view of all the connected computers. So this is why I ended up with basically two separate programs into one.






http://www.efmer.eu/boinc/boinc_tasks/

As of version 1.6.71 the installation no longer includes the VS2005 runtime package (Redistributable).
Due to a lot of problems, I included the code in the actual exe.
The download and installation are now a lot faster.
This makes the code somewhat larger, but the actual footprint in memory should not be larger.

When you are completely sure that no other program is using the Microsoft Visual C++ 2005 redistributable , you may remove it.

V 0.03 in 32 and in 64.

There is a new Beta version on the beta download page.
On the download page you can find all the changes made in this new version.
http://www.efmer.eu/boinc/download.html

There is some new text that is not yet translated.

[if gpu temperature < 58 email reset 68]

For most users the rule composer will be enough. But for those who want everything , here is some more detailed information.

Some specials are execute1 , execute2, execute3. What they do is start a batch file execute1.bat, execute2.bat or execute3.bat.
The batch file must be located in the same directory a TThrottle.exe.

Can I change the annoying alarm sound? Sure, find another sound and place it in the same directory as TThrottle.exe, next rename it to alarm.wav.

Why a system reboot? Sometimes a BOINC project program crashes. One of the ways to see this is to watch for the CPU or GPU temperature.

I personally use this rule on one of my computers:

if gpu temperature < 58 email reset 68
When the gpu temperature goes above 68 degrees the rule becomes active. If the gpu temperature goes below 58 degrees an E-Mail is send.

if gpu temperature < 56 reboot reset 70
When the gpu temperature goes above 70 degrees the rule becomes active. If the gpu temperature goes below 56 degrees the system reboots itself.

if cpu temperature > 90 hibernate
When the cpu temperature goes above 90 degrees the rule becomes active. The computer will go into hibernation (sleep).

if cpu temperature > 93 shutdown
When the cpu temperature goes above 93 degrees the rule becomes active. The computer will shut itself off.

if time 01:00 reboot
On a computer running GPU tasks it is sometimes a good thing to reboot your computer on a regular basis.

Long time unattended running

I sometimes want to let one of my computers run, when I'm on vacation.
To set up a simple watchdog function, I select in the computer BIOS to start when the power is switched on.
Next I plug the computer power in a timer, that shuts down the computer power at 01:00 (OFF) and connects it to the mains again at 01:01 (ON)

In TThrottle I set the rule:
if time 00:55 shutdown
This shuts the computer down before the timer switches off the main power.
If the computer for some reason hangs, it is still rebooted but not as elegantly.


Warning: a reboot or shutdown does not save any work. It just shuts down as fast as possible. And putting (or letting) BOINC in snooze mode (suspend) will also trigger this rule, when triggered on a temperature. So this if for a BOINC only machine.

The lowest setting is 1%, even if you put in less, TThrottle only goes as low as 1%.

Why? Because otherwise programs may not get enough time to run. As most programs are not tested for this, because Windows will always allow programs to run a minimum amount of time.

If a program would be stopped for some time, it may become instable, unpredictable and even crash.

And if at 1% the CPU or GPU still gets too hot  , something else is wrong..

And you can always set the automatic shutdown at the maximum temperature, so the system shuts down gracefully, in the event of overheating

Signed drivers 32/64 are now part of the regular installer as of V 1.58.

Run sigverif to check if the drivers are signed.

Everything in this Tab is a bit experimental so take extra care and report any problems to me.

When clicking on this tab you get the message:

You need to enable TThrottle by setting "Auto Active" otherwise this will not work.
If you don't need the throttle set the temperatures to a high setting.

"Enable Graph"
A graph is drawn of the total runtime (process and threads).
The white line is the overall total run time so far, in a percentage of the core run time.
The yellow line is the actual run time per second, in a percentage of the core run time.

"Enable Text"
Text is displayed, with info about the Process and its Threads.
You can see the Kernel (Windows) and User (Program) run time as well as the current priority assigned to the process and its threads.

Priority setting: See other chapter in this forum


Feature supported as of V 1.58

Checkout the manual: http://www.efmer.eu/boinc/tthrottle_manual.html#threads_tab

You need to enable TThrottle by setting "Auto Active" otherwise this will not work.

The CPU/GPU feeder program, called something like MB_6.08_CUDA.exe, feeds the CPU with data (CUDA).

To keep the GPU busy it is essential that the CPU keeps sending data as fast as possible, failing to do so can mean that less work is done.
TThrottle has a tab called "Thread" and a priority setting. Normal this is set to "Keep" this means TThrottle doesn't change a thing.
By clicking on "Text" you can see the current priority settings of the program and its threads.
Elevating the priority  to "Below Normal" or "Normal" can get you a better feeding of the GPU.
The downside is that other programs get less time assigned, so this may cause the keyboard to freeze at times. If this features gives some results (feedback please) I will add a method to switch this on, only when the computer is not in use.

WARNING: A priority setting above Normal may create an instable system as there may not be enough time for other critical tasks! So be aware of the danger. A higher setting than normal is only to be used on a system with at least 4 cores and even than the results may be unpredictable.

Thread: Is a program started by the main program.

Priority: The higher the priority the more likely the program or threads get time assigned to it to run.
From high to low the priorities are: High - Above Normal - Normal - Below normal - Low (idle).
Idle threads run only when the system is not busy with anything else. This is the normal project setting of projects running in BOINC.

PID: Program identifier, all running programs and threads have a unique number assigned to it.

Kernel: The Windows program doing something for the program or thread.
User: The program or thread itself.

Feature supported as of V 1.58

Checkout the manual: http://www.efmer.eu/boinc/tthrottle_manual.html#threads_tab

As of version 1.73 this feature is no longer part of the default installation. On the download page look for TThrottle Special Edition.

A stand alone version is now available:

http://www.efmer.eu/forum_tt/index.php?topic=198.0