tasks that use 1.00 GPU and 1.00 CPU escape Tthrottle control during high CPU temp events.
CPU is not checked for these tasks.
from the log:
97%: Cpu: einsteinbinary_ABP2_3.11_windows_intelx86__ABP2cuda23.exe, PID: 5812, Threads: 3
27 October 2010 - 08:44:34 Number of matching Programs (Processes): 2
Cpu: einsteinbinary_abp2_3.08_windows_intelx86.exe, PID: 5004, Threads: 3
Gpu: einsteinbinary_abp2_3.11_windows_intelx86__abp2cuda23.exe, PID: 5812, Threads: 3
--------------------------------------------------------------------------------------------------------------------- 1 0 1 0
this allows overheating until the universal throttle rule kicks in.
Interesting, that's a problem right now, that will not work as it should.
This will probably need a more drastic fix. ???
Yes, I've noticed this too a few months ago, it requires an "(indeed also a CPU) exception from an (it is a GPU) exception" ;D
I wanted to report it back then, but then I've solved it by manually adding some Einstein executable(s) (tomorrow I can tell exactly) to Programs tab / "Expert" checkbox / exe.cutable name substring + "[ v Add v ]" to Programs list. (I've recalled that Fred made me aware of this nearly a year ago.)
Maybe the BOINC tab should contain some more straightforward way to add exceptions to GPU substrings, like an additional "Include CPU" + "[ v Add v ]" + "[ ^ Remove ^ ]" section brlow for adding exe substrings, which should override the GPU section above?
Pepo :
<< I've solved it by manually adding some Einstein executable(s) (tomorrow I can tell exactly) to Programs tab / "Expert" checkbox / exe.cutable name substring + "[ v Add v ]" to Programs list.>>
I did that (which is fine for me) but others may need the program to work "out of the box" as it were. I hope the program becomes a "turn-key" function for everyone to use.