Forum > GPU crunching
AK V8 + CUDA MB team work mod
k6xt:
--- Quote from: Raistmer on 08 Feb 2009, 02:43:46 pm ---in stderr of finished result.
On web site go to result info
--- End quote ---
Would that be this statement? If so I don't understand the stated time.
"Wall-clock time elapsed since last restart: 6902.6 seconds
called boinc_finish"
Also the above statement doesn't seem to exist in all completed WU that have been granted credit. Is this statement a part of your work and applies only to GPU-crunched WU?
Sorry for the bandwidth....just trying to understand what is happening.
Yellow_Horror:
How you like an idea to combine "VLAR stays on CPU" with "Advance to free GPU" techniques?
For example, let 3 WU's are crunched at 2core+1GPU system. The GPU task is finished up, take the new one - oops it's VLAR - stays on the CPU. For some time 3 WU's are crunched on CPU, then one of the previously running non-VLAR tasks will detect free GPU and switch to it.
Yes, it can end up in 3 VLARs crunching on CPU while GPU stays idle. But with more cores the situation is less probable. The main advantage of this scheme is that VLAR is never end up on the GPU giving the lazy uzer interface.
I am interested to test such version if you decide to create one (my CPU is limited to SSE3).
Raistmer:
--- Quote from: k6xt on 08 Feb 2009, 07:36:37 pm ---
--- Quote from: Raistmer on 08 Feb 2009, 02:43:46 pm ---in stderr of finished result.
On web site go to result info
--- End quote ---
Would that be this statement? If so I don't understand the stated time.
"Wall-clock time elapsed since last restart: 6902.6 seconds
called boinc_finish"
Also the above statement doesn't seem to exist in all completed WU that have been granted credit. Is this statement a part of your work and applies only to GPU-crunched WU?
Sorry for the bandwidth....just trying to understand what is happening.
--- End quote ---
It's elapsed time value. From lats task restart or from beginning of task if there were no restarts.
This output now added o all new "team" builds.
Richard Haselgrove:
Heads-up for people testing out the latest Alpha BOINC clients, and fiddling with cc_config.xml settings.
--- Quote from: John McLeod VII ---The setting of <ncpus>0</ncpus> is NO LONGER the way to set it back to whatever the computer has (and I have this as a place holder on several machines). It has to be <ncpus>-1</ncpus> to work. Perhaps a warning about this should be put in the config documentation page is it is a rather nasty and hard to figure out problem.
--- End quote ---
--- Quote from: David Anderson ---That's right; I recently changed things so that <ncpus>0</ncpus> means use zero CPUs (this was in response to a request from someone who wanted to compute only with GPU).
To get the actual #CPUs, use -1 or omit the element.
--- End quote ---
Archangel999:
Raismer there is some kind of bug i use the ak v8 + cuda mb mod and cc_config file to crunch 5 at a time work unit but at some time after working it is stoped crunch the 5-th unit it the boinc it says it is runnig but no progreess and the cpu is not at 100% after that :o it is 75% again and after some time it goes only 50% and cunching only 3 work unit the other 2 says again in boinc that they are runnig but no progress when i go to the task manager they are in the memory but maybe they are stuck ?
or mayby have to start the cuda log but it is for cuda only here they are a cpu applications ???
and cuda log work perfect but the app that freezze is AK_v8b_win_SSSEx_GPU_CPU_team.exe*32 but why is 32 bit will you do 64bit for windows like mine xp x64 ??
and with some time the windows has prompt me a error message from this application when it stuck
Best Regards
D.Draganov
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version