....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 cores2) 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)
4) How many CUDA MB processes running in system at this time 1 on only GPU, 'Waiting to Run'
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ? 3 x AP 5.03 (1 per CPU core +1 )2) What access state of GPU_lock file (is it accessible or not) Opens as empty file in notepad without complaint.3) Is any progress inside state.sah of task being in "waiting" state. Not visibly, though timestamp was incrementing every checkpoint period etc4) How many CUDA MB processes running in system at this time Only the 1 'Waiting to run"5) temp of GPU (busy or idle).Busy 75C (normal), if run ATITool at same time, no artefacts.
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ? At this time I would have 4 AstroPulse work units running on 4 CPU cores.2) What access state of GPU_lock file (is it accessible or not) I do not have this file or where it is at. Only have "boinc_lockfile" located in slots folders.3) Is any progress inside state.sah of task being in "waiting" state. Included here are 2 state files captured several minutes apart.4) How many CUDA MB processes running in system at this time Only the one (1) that is showing "waiting to run" in Boinc Manager.5) temp of GPU (busy or idle). 65C busy, 56C idle.
Ageless posted here............http://setiathome.berkeley.edu/forum_thread.php?id=52090&nowrap=true#869394This may be a Boinc problem? If so my apologies to Raistmer.
Okay, so why the massive 1.94 credit claim on my full length no progress run ? (See updated run info)It seems there are no function calls to accumulate the flops while it is running. (compute_fraction_done or whatever Cuda app uses) [Edit: It will be interesting to see what the Wingman Claims).
[Damn it's working no beer for me ]Jason
I'm sure we can sort something out if you join Matt on his tour of Lancashire, Yorkshire, Nottinghamshire, Cambridgeshire....