So.... not advised to run with current Astropulse only work climate then, lest you get NumGPUs over subscription... right?
Quote from: Jason G on 28 Feb 2009, 06:29:49 amSo.... not advised to run with current Astropulse only work climate then, lest you get NumGPUs over subscription... right?Anything else than SETI MB could result in overloaded CPU and idle GPU if leaved w/o user intervention. Lack of BOINC ability for project pairing make it impossible to be sure at least one task allocated for SETI MB and CPU->GPU rescheduling is possible only inside teamed SETI MB programs.
Thank you for the new release, it is working great on my system. I have one complaint thou. Throwing out the VLAR WU... It is a shame, I was just looking to the Boinc client and I saw 12 of them beeing rejected one after another. I don't think it is fair to the other wingman.Is there a way that this can be solved without autokill? Like force them to the CPU instead of GPU? What happens if there are not killed - under V10 app?
Probably only active user profile can interact with GPU.
Quote from: Raistmer on 28 Feb 2009, 04:00:43 pmProbably only active user profile can interact with GPU.How about if I install the program in Protected mode? Will this allow BOINC to run while there is no one logged in and still use the GPU with CUDA?-V
They take days like this and I haven't seen any CUDA or AK WU's forever. Any ideas?
i'm running boinc 6.6.11 and V10a and can't get any of the AP units to run on the gpu. right now all i have is AP work units and am running 9 MB app simultaneously. this has been reproduced on my other four computers with gpu's.The GPU temp is low and task manager says everything is running on the cpu as i do not see any cuda executable running in task manager.all i see is six occurrences of "ap_5.03r112_sse3.exe*32"