Forum > GPU crunching
Ok, I give up
Azzitude:
Where is this phantom cc_config.xml file located at?
Raistmer's_opt_package_V8a_CPU_GPU_team_SSE3 not in here
and not in ANY of the Boinc diectories, did a full search on C drive and nothing ... now all I have running is 8 WU with NO gpus ......H E L P
Windows Vista Ultimate 64 Bit and 2 260's sittin Idle
Yellow_Horror:
--- Quote from: Azzitude on 16 Feb 2009, 02:08:43 am ---Where is this phantom cc_config.xml file located at?
--- End quote ---
There is no such file by default. You need to create one into your BOINC data directory (where are client_state.xml and some other files located).
P.S. Do you know that V8 package don't support multiple GPUs? Maybe V7 is better for your config.
See http://lunatics.kwsn.net/gpu-crunching/modified-seti-mb-cuda-opt-ap-package-for-full-gpu-utilize.0.html
Raistmer:
http://lunatics.kwsn.net/gpu-crunching/modified-seti-mb-cuda-opt-ap-package-for-full-gpu-utilize.msg12177.html#msg12177
Azzitude:
ok, thanx for that ... but now another, running the stock app it showed CUDA running at 0.20 on each file and now it shows 0.04 on each file and only 5 wu on cpus for a total of 7, any thoughts?
Josef W. Segur:
--- Quote from: Azzitude on 16 Feb 2009, 08:00:44 am ---ok, thanx for that ... but now another, running the stock app it showed CUDA running at 0.20 on each file and now it shows 0.04 on each file and only 5 wu on cpus for a total of 7, any thoughts?
--- End quote ---
Running stock, the Scheduler estimates the speed of the GPU and combines that with the host Whetstone benchmark to estimate what fraction of a CPU core will be needed to feed the GPU. Running with an app_info.xml there's just whatever <avg_cpus> that file has specified. If you want a reasonably accurate value, use Task Manager to find out how much CPU is actually used feeding a GPU and edit the app_info.xml. Even if you don't edit the file, the Task Manager check is worth doing so you know (and we'd be interested too).
I don't know why only 7 are running, IIRC others have seen oddities which disappear at the next task switch interval.
Joe
Navigation
[0] Message Index
[#] Next page
Go to full version