TThrottle is not throttling Milkyway@Home gpu tasks on 3.52

Started by book_wyrm, April 27, 2011, 01:43:05 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

book_wyrm

The task for the post above took 3,414.82 seconds real time and 25.62 seconds CPU time

My current task at the moment is overheating again.....
Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 5020, Threads: 5
CPU:0, GPU:1, PID:5020 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114912_1304776310
'Connect with BOINC client' was off this time when the task switched

book_wyrm

WU in last post took 3,181.23 seconds in real time and 16.75 seconds CPU time

Current WU:
CPU:0, GPU:1, PID:3776 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114911_1304776310
Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 3776, Threads: 5
'Connect with BOINC client' was checked when task switched. Still needs TThrottle to restart to throttle temps.

book_wyrm

WU in last post took 3,519.92 seconds in real time and 24.69 in CPU time.

Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 4068, Threads: 5
CPU:0, GPU:1, PID:4068 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114904_1304776310
'Connect to BOINC task' was unchecked when the tasks switched.

book_wyrm

The task in the last post had a compute error but it may be of interest to note that after running 721.57 seconds in real time the task only required 6.04 seconds in CPU time.

book_wyrm

CPU:0, GPU:1, PID:4072 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114888_1304776310
Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 4072, Threads: 5

'Connect with BOINC client' was checked when task switched

fred

Quote from: book_wyrm on May 07, 2011, 04:01:40 PM
The task in my last post took 3,131.24 seconds real time and 15.49 CPU time

CPU:0, GPU:1, PID:3332 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114924_1304776310
Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 3332, Threads: 5
This task initially had "Connect with BOINC client" ticked
In a week or so, I'm back home, so I will do some MW testing.

book_wyrm

Shall I stop posting overheating task information until you get back? Do you have enough information now? Let me know if you need anything else.

fred

Quote from: book_wyrm on May 07, 2011, 04:01:40 PM
The task in my last post took 3,131.24 seconds real time and 15.49 CPU time

CPU:0, GPU:1, PID:3332 (5)   Slot:1   http://milkyway.cs.rpi.edu/milkyway/   de_separation_10_3s_fix20_1_114924_1304776310
Gpu: milkyway_0.52_windows_intelx86__cuda_opencl.exe, PID: 3332, Threads: 5
This task initially had "Connect with BOINC client" ticked
Can you give me the TThrottle log, just after startup, so I can see what system you are running.
Are you running a regular GPU task on Milkyway? So just as it is, no special versions.

book_wyrm

I've PMed the log to you. It's after a TThrottle restart after a high GPU temp.
I'm using the stock cuda application from Milkyway.

fred

Quote from: book_wyrm on May 07, 2011, 10:30:05 PM
I've PMed the log to you. It's after a TThrottle restart after a high GPU temp.
I'm using the stock cuda application from Milkyway.
One last question, when you snooze the GPU only, what is the temperature, before and after the snoozing (wait for a minute or 2).

book_wyrm

It dropped to 60 when I snooze the GPU. I've set TThrottle to have a max temp of 75.

Edit: After unsnoozing the GPU the MW task that was running restarted and gpu started to overheat again. I had to restart TThrottle as usual.

fred

Quote from: book_wyrm on May 08, 2011, 12:04:11 AM
It dropped to 60 when I snooze the GPU. I've set TThrottle to have a max temp of 75.

Edit: After unsnoozing the GPU the MW task that was running restarted and gpu started to overheat again. I had to restart TThrottle as usual.
I know enough for now, thanks.

fred



fred

Quote from: book_wyrm on May 08, 2011, 12:22:39 AM
The stable version 6.10.60
Can you try running TThrottle as Administrator.
With the right mouse key run as... maybe it's an access problem.