Forum > GPU crunching
It works!
Jason G:
Well I waited an hour, and it never finsihed. I can certainly plug the app in again and watch the state.dat when it freezes. It seems to be a regular occurance at least with this particular app, and Boinc combination (And I do suspect Boinc's scheduling behaviour is to blame pretty strongly).
Shouldn't take long.
Raistmer:
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).
Jason G:
I can answer most of those now, will update remaining ones at next lockup
--- Quote from: Raistmer on 25 Feb 2009, 11:55:49 am ---....
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 x AP 5.03 on CPU cores
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
1 on only GPU, 'Waiting to Run'
5) temp of GPU (busy or idle).
Busy, Full load temp ~75C ( not overheating for this GPU either, no screen jerkyness or other apparent issue, can still run ATI Tool with no Artifacts)
--- End quote ---
Raistmer:
--- Quote from: Jason G on 25 Feb 2009, 12:04:20 pm ---
4) How many CUDA MB processes running in system at this time
1 on only GPU, 'Waiting to Run'
--- End quote ---
I meant OS processes, not BOINC ones.
And it seems you don't use ncpus field? why only 2 AP tasks on dual core + GPU ?
Jason G:
Read original my post again. I tried both ways. If you want me to do this with ncpus=3 .. will do.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version