Topics

I want to detect if a ATI or NVIDIA gpu is running a tasks.
So I'm only interested in GPU tasks.

1) NVIDIA do all tasks show + x.00 NVIDIA GPUs = xNV in the Use column. I mean on all projects, or are there projects that show something else.
2) ATI what do these tasks show in the Use column. Are they all the same, on all projects.

V 1.90

A lot of changes, deep in the program, so be careful.

Changed: Show NVIDIA and AMD/ATI cards in mixed systems.
Changed: The max number of GPU cards is 6.
Changed: Add __ati as default to the GPU list, when empty.
Changed: The mini window width is better calculated.
Changed: Revised driver V 2.0 that can handle more than 8 cores.
Changed: Adaptable temperature read from driver, reading only the cores needed.
Changed: The maximum number of temperature cores is 8, the maximum number of virtual cores is 16.
Fixed: RNA World puts play.exe in a slot. TThrottle added everything with play in it, like wmplayer.exe to the CPU list.

This is a pre release version.

Place the exe in an empty folder without any dll's, this is an English only version.

http://www.efmer.eu/download/boinc/tthrottle/TThrottle_184_pre.zip

Changes can be found here: http://www.efmer.eu/forum_tt/index.php?topic=50.0

[Add rule]

Some examples

If project X with application Y is active for more than 3 hours an event is triggered.
If project X with application Y generates 10 errors within 10 minutes an event is triggered.
If any task has a progress of less than 0.01% within 10 minutes an event is triggered.
If project X with application Y runs below 56C for xx time it will trigger an event.
If 10 errors appear within xx time an event is triggered.
If computer X lost the connection for xx time an event is triggered. If the computer is reconnected within the xx time the rules isn't triggered.
If project Y on computer X has more work than 1 day set "No more work".
If project Y on computer X has less work than 12 hours set "Allow new work".



It is possible to add a rule from the Tasks view. Click on the task you want add a rule for and press the right mouse key.
Select Add rule
This fills in all the names relevant for this task.

Rule name: Must be unique name that describes the rule.
Computer: Optional name of the computer, leave this empty if the rule applies to all computers.
Project: Optional name of the project, leave this empty if the rule applies to all projects.
Application: Optional name of the application, leave this empty if the rule applies to all applications. As of V 1.28, wildcard may be used like t?s? = test, test* = test1whatever, test* = test2

* the above fields may hold a part of the name: Like 3.02, instead of the whole name.

Type:

Elapsed Time The time the task has been running since the first start.
Cpu% The percentage between wall clock the actual run time of the CPU.
Progress % The progress percentage of the task.
Time left The time the task has left.
Progress / min % As the Progress % but now the progress that has been made in one minute.
Use The number of CPU and GPU % that are planned for this task. E.g. 0.04 Cpu + 1 GPU or 0.025Cpu.
Temperature The CPU or GPU temperature. This rules must have a valid computer name.
Wallclock In a time interval. This rules must have a valid computer name.
Deadline Deadline =  (Deadline time - System time) - Time Left. So a deadline that is 1 day from now and time left of 2d gives -1d, that means it will go 1 day beyond the deadline. < -14d,00:00:00 triggers if 14 days or more past the deadline. < 4d,00:00:00, triggers if 4 days or less, before the deadline.
Time Left Project Cpu and Gpu time left on a specific project.

The 3 rules have to be ALL valid, at the same time for the event to trigger.
You may leave unused rules empty.

Time:

The time the rule has to be valid to produce an event. Blank means 0 seconds.
Don't use a short time, as this may result in a lot of false positives.

Event:

A rule may have one internal an one external event at the same time.
E.g. Suspend a task and start an external program.

A rule may have 0 events, so it only shows a color.

Run program Runs an external program or batch file.
The field below must hold the full name of the program. E.g. beep.bat
The folder is the default BoincTasks folder: C:\Users\user name\AppData\Roaming\eFMer\BoincTasks\

So beep.bat is the same as C:\Users\user name\AppData\Roaming\eFMer\BoincTasks\beep.bat

An ENTER (key) may be used to keep the text in the box.

You may add parameters: E.g. beep.bat, parameter
The "," is used to separate the program name from the parameter.

Suspend project

Suspends the project of the task that triggered the rule.

Suspend task

Suspends the task. When more tasks are triggered at the same time, only one is suspended. The other tasks are suspended, one every following second.

No more work

Sets the project to "No more work". E.g. Deadline < 2d,00:00:00 No more work.

Allow new work

Sets the project to "Allow new work". E.g. Deadline > 2d,00:00:00 Allow new work.

Snooze

Snoozes the entire computer for a time set in the right corner window, like 30:00. (30 minutes).
To allow the computer to run again, set a time of 00:00 (0 second), this will remove the snooze condition.

"show logging" check

When checked, BoincTasks will show the rules logging window, when an event is triggered.

Resetting a rule:

Rules are reset when you:

Edit any rule.
A tasks is no longer running.


Some inside information:

The rules are checked, using the history information.
This means, the rules are checked, at the history interval time.
CPU % and Progress / min are measured, over a period of 2 History cycles.

Progress / min:

Cycle 2: Progress 61   1 Progress / min
Cycle 4: Progress 64   3 Progress / min
Cycle 6: Progress 66   2 Progress / min
Cycle 8: Progress 66   0 Progress / min
Cycle 10: Progress 66   0 Progress / min

Rules can be used on a specific computer, or on all computers, unless stated otherwise.
Leaving a rule field empty, is the same as a all.
So a blank computer = all computers, a blank project = all projects, a blank program = all programs.

The rules below are specials.

Status rules:

Status rules can trigger on a number of tasks in a specific status.

The syntax for the value is: status, count 3,4
A rule can only have status types, all others types will be ignored.
A status rule must have a valid computer and project name. An Application name will be ignored.

Examples:

A rule Status > 3,4 Time 10:00 is active when there are 4 tasks in the error status in the last 10 minutes.
A rule Status = 5,0 Time 60:00 is active when there where no completed tasks the last 60 minutes.


Status codes:

3 Computation error
4 Uploading
5 Ready
6 Aborted


Wall clock rules:

As of V 1.52.


Wallclock time rules can:
Suspend and resume work fetching.
Suspend and resume specific projects.
Snooze and resume CPU and or GPU on a computer.

Select "Wallclock" in the Type column.

Click on the schedule and modify it.

The shift key lets you select a range.
Together with the Ctrl key a range can be deselected.

Connection rules:

You can setup a rule, that goes active, when a connection is lost or never made, after xx seconds.
The Project, Application and Value fields aren't uses.
A blank computer name means all computers.
=<> A lost connection
<> No connection

Connection =<> 00:05:00 (Type, Operator, Time) When a connection is lost for more than 5 minutes the rule triggers.

The only Event that can be used is "Run program" or "Show" logging.

Time left on a project rules:

Make sure you set a valid computer and a project, the application name isn't used.

E.g.
Time Left Project > 1d,00:00:00 will trigger if the project has more than 1 day work. Typically "No more work" is used as Event.
Time Left Project < 0d,12:00:00 will trigger if the project has less than 12 hours work. Typically "Allow new work" is used as Event.

Warning use a time of 2:00 on the  "Allow new work" rule, to make sure it isn't triggered at start up, when the time left is 0, for a short while.

--------------------------------------------------------------------------------------------------------

The rules are stored in C:\Users\username\AppData\Roaming\eFMer\BoincTasks
File: rules.xml

itime = trigger time in seconds
ivalue0 if time than in seconds

Fixed: The 32 bit version doesn't show the list boxes on some computers.

Changed: TThrottle now sends the computer name to BoincTasks: <TThrottle><HN: computer_name>
Changed: Multi language installer.
Fixed: Clicking on an empty rule list, gave an message box with a parameter error.
Fixed: An active rule didn't show in the color red.

The following members will be removed:

All members that have never posted and haven't been on-line for 365 days.
All members that have never logged in. (within a week).
All members that have never posted and are on http://www.stopforumspam.com/

This leaves only us the active board members.

For more information see: rules

Request new rules, but not too specific.

I am planning this feature to be gradually included in the next versions.

Most "small" networks have some sort of simple  dynamic IP address allocation.
But this doesn't work well with BOINC as it is difficult to determine the computer on the other side.
On most the computers the name <-> IP address conversion will not work.

I want to add a feature to do this automatically.

Setup requirements:

1) IP range like 192.168.10.1 to 192.168.10.255 and a port to use.
2) Password: A BOINC password for all computers in the net, MUST be the same.
3) BOINC on all remote computers must allow computers from the net to access it. (allow IP and use the same password)

The computer list only holds the local machine and computers that are not on the net.

A) BoincTasks will check the entire net, this will take from 1 - 10 seconds to get all the connected computers.
B) BoincTasks will get the host name of all the connected computers and will add them, temporarily to the computer list.
C) BoincTasks will show all these computers.
D) At a specified interval BT will check if there are new computers with BOINC on the net and add them to the list.
E) Computers that are no longer in the net / unconnected, will be removed from the list.

Under Windows 7 it is best to let TThrottle run with administrator rights.

To do so:

Right click the programs executable, click Properties > Compatibility (tab)
under "Privilege Level" check the box that says "Run this program as an Administrator" > Apply > OK.

The only problem is you have to do this every time you install an new version.

(Changed): Moved from compiler V 2005 to V 2010.
(Changed): Driver installer V 1.30 now shows Windows 7 machines.
(Changed): Rules tab -> Show running processes: Moved process fetch an calculations to another thread. Makes the load more distributed on multi-core CPU's.
The same thread determines the runtime % minimum threshold for the general throttle.
(Changed): General throttle: only throttles processes that use op more that 4% or a core time. This eliminates the huge list of background processes from throttling.
(Changed): Increased height of the dialog, needed as CPU's tend to get more cores.
(Changed: One unified installer for 32 and 64 bit.
(Fixed): A potential crash may occur. (Close an already closed handle).

I updated the manual. Please check it out, report any grammatical errors.

When you are missing something important, that new users should know, let me know.

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

BoincTasks has several filters that combine tasks of the same project and name.
This will get you a way better, condensed view of what's going on.

Filters can be set and removed in the extra->Filter menu. These filters are set for all computers at the same time.

If you want to disable a filter quickly, just double click on a filtered group and the filter is temporarily removed and just for that one computer.
To enable the filter again, double click on any tasks, that was previously filtered and the filter is restored.

The computer side bar shows 2 icons that informs you about the connection status.

There is no connection.
There was a connection but now it's lost.

Clicking on the computer tab gives you some more information about a computer with no connection.

To reconnect:

Click on "all computers" in the computer sidebar or click on a single computer that you like to reconnect. This will start a reconnect sequence.

If you want BoincTasks to try reconnecting on a continues basis, set up a reconnect: Settings BoincTaks - > Extra and fill in 120 in the "= Reconnect every xx seconds".
This will autoconnect every 2 minutes. The downside is that this takes time and may slow down the viewing.

More information about why a connection is lost can be found in the computers tab.

You want more information in the logging?
Change the log.xml in C:\Program Files\eFMer\BoincTasks\log
Set this option:       <connecting>         1   </connecting>

You find a copy of log.xml in C:\Program Files\eFMer\BoincTasks\examples\log , copy the file to C:\Program Files\eFMer\BoincTasks\log and restart BoincTasks.

Has anyone got BT working on a 64 bit machine with a remote computer connection?

V 1.76: Released April 2010

Changed: A special regulator with large amounts of processes.
Changed: The list is automatically rebuild quicker, when throttle levels are below 6% was 15%. (less overhead when the throttle is close to max).
Changed: Exclude BoincTasks.exe from the general throttle.
Changed: The general rule timer from 2 to 4 seconds.
Fixed: A rare TThrottle crash.

Jim wrote this nice article that may help others.

Summary:
o Comodo and avast! virus scan overheating solutions with TThrottle
o Rules question
o Configuration

1. Comodo and avast! virus scan overheating solutions
I'm running a GigaByte EX58-UD3R-SLI board (i7 processor) under Vista 64. I worked the last two days with TThrottle 1.75 trying to overcome a heating problem when BOINC tasks and COMODO Internet Security virus scans are running at the same time. I saw the hint on your forum to try Avast!, but this displays the same problem.

It turns out that both comodo and avast! have self protection features that disable throttling the scans. I've attached a PDF file with screen shots and instructions to disable these features and restore temperature control by TThrottle. The "protection" appears to make these exe files run as "SYSTEM"  rather than "Administrator" or "User". With the Task Manager, you can see the change.

See pdf below.

Jim uses the rules tab throttle.

tthrottle_avast_comodo.pdf

This shouldn't happen but sometimes it does.
What to do: What to do if BoincTasks frequently crashes

V 1.75

Changed: Processor Signature: 000006FD Processor: Intel(R) Core(TM)2 Duo CPU     T5250  @ 1.50GHz : TJunction is now 85C.
Added: Catalan language.

If you like our program, help us to continue our work.

Using Paypal or a credit card.
Donate TThrottle

You can donate here in Crypto:  Coinbase

Every donation $50 and up will be shown in the about box.