Forum > GPU crunching
CUDA MB V12b for multi-GPU multicore hosts.
Raistmer:
Ok, my own and Pappa's tests show that V12b unneeded for single GPU hosts.
That is, no advantage to use on non-targed hardware.
Raistmer:
@glennaxl
PM sent.
Sutaru Tsureku:
Raistmer, I have one, two questions.. :-[
SETI@home/NC subforum/'eFMer Priority' - (CUDA) app priority change- [Message 959115]
Which forum you prefer, here or there?
Raistmer:
--- Quote from: Sutaru Tsureku on 30 Dec 2009, 08:39:08 pm ---
Raistmer, I have one, two questions.. :-[
SETI@home/NC subforum/'eFMer Priority' - (CUDA) app priority change- [Message 959115]
Which forum you prefer, here or there?
--- End quote ---
I answered most of these questions few times already.
Once more - no, Windows not smart enough to do priority based scheduling through different cores.
About changes between V12b and V12 - most probably small speed variations you see comes just from different binaries.
If you pay attention to other tests published you will see that this difference pretty variable one.
+ limiting number of cores available for app will inherently lead to some small (or not so small - it strongly depends from system load pattern) slowdown.
This was explained in some thread too. This is some kind of tradeoff: loosing some speed under one set of conditions to get boost under another.
And again once more, V12b intended to fight possible x2 (or x3 if 3 GPU processes launched on same core) slowdowns. If you don't see such slowdowns with V12 now - no reason to use V12b.
About priority - still didn't see your tests w/o EFmer's priority tool for V12b. Do you see difference in speed or not??
Raistmer:
@glennaxl
could you attach (zipped) logs from those 8 CPU benchmarks you ran with 3 or 2 GPUs together for results you posted earlier. It will give full picture, thanks in advance.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version