Forum > GPU crunching
It works!
Yellow_Horror:
--- Quote from: Raistmer on 25 Feb 2009, 11:55:49 am ---I need to know if "refuse to die" mod works or not. If it not work indeed I remove it from CUDA MB.
So I need next info on this topic:
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
2) What access state of GPU_lock file (is it accessible or not)
3) Is any progress inside state.sah of task being in "waiting" state.
4) How many CUDA MB processes running in system at this time
5) temp of GPU (busy or idle).
--- End quote ---
It seems to be two different types of "wrong" behaviour on my system.
The first one is the app freezes at 3 seconds of CPU time with progress 0%. The GPU is idle (as shown by nVidia System Monitor by "GPU Usage" and "GPU Temp" parameters). Suspend/Resume the task don't help (no new task is started, no progress of the freezed task after resume). Stop/Restart BOINC help - the previously freezed task run normally and crunching continues... until next freeze. Sorry, no info about gpu_file_lock and state.sah at this moment. Will see at the next freeze.
The second variant is a task suddenly receive "waiting to run" state in the BOINC Manager. The GPU seems to be working, gpu_file_lock is locked, state.sah is renewed timely. Now i wait if such task will be ended in time.
Yellow_Horror:
The "Waiting to run" task is ended (suddenly to BOINC) and reported.
http://setiathome.berkeley.edu/workunit.php?wuid=404255137
Claimed credits seems to be low :(
Jason G:
--- Quote from: Yellow_Horror on 25 Feb 2009, 02:54:54 pm ---...
Claimed credits seems to be low :(
--- End quote ---
Better than my lousy 1.94 credits, LoL ;D
Yellow_Horror:
--- Quote from: Jason G on 25 Feb 2009, 03:23:56 pm ---
--- Quote from: Yellow_Horror on 25 Feb 2009, 02:54:54 pm ---Claimed credits seems to be low :(
--- End quote ---
Better than my lousy 1.94 credits, LoL ;D
--- End quote ---
My task stuck at about 30%, your at 1.712%. Probable it makes sense.
Yellow_Horror:
I notice another sign of strange behaviour:
--- Quote ---26/02/2009 16:13:14 SETI@home [task_debug] result 16ja09ab.7620.1708.12.8.217_2 checkpointed
26/02/2009 16:13:16 SETI@home [cpu_sched] Preempting 16ja09ab.7620.1708.12.8.217_2 (removed from memory)
26/02/2009 16:13:16 SETI@home [task_debug] task_state=QUIT_PENDING for 16ja09ab.7620.1708.12.8.217_2 from preempt
26/02/2009 16:13:17 SETI@home [task_debug] Process for 16ja09ab.7620.1708.12.8.217_2 exited
26/02/2009 16:13:17 SETI@home [task_debug] task_state=UNINITIALIZED for 16ja09ab.7620.1708.12.8.217_2 from handle_premature_exit
26/02/2009 16:13:17 [coproc_debug] freeing 1 of coproc CUDA
26/02/2009 16:13:17 [work_fetch_debug] Request work fetch: application exited
26/02/2009 16:13:17 SETI@home [cpu_sched] Starting 16ja09ab.7620.1708.12.8.217_2(resume)
26/02/2009 16:13:17 [coproc_debug] reserving 1 of coproc CUDA
26/02/2009 16:13:17 SETI@home [task_debug] task_state=EXECUTING for 16ja09ab.7620.1708.12.8.217_2 from start
26/02/2009 16:13:17 SETI@home Restarting task 16ja09ab.7620.1708.12.8.217_2 using setiathome_enhanced version 608
--- End quote ---
This is repeated every few minutes, dropping overall performance.
I use BOINC 6.6.10. Is such behaviour normal or not? Must i report it to developers as a bug?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version