Joined: 16 Jun 01
Not quite. For the same reason, If GPU requires CPU and CPU busy with processing from other GPU app instance one still get slowdown. So, more cores would require in few GPU or few tasks per GPU configs.
(Need to note, that this slowdown, at least for ATi cards, has statistical character. That is, time to time whole GPU AP task can be completed on fully loaded CPU w/o any slowdown. But time to time slowdown so big that task can be even aborted by BOINC).
Could you describe how these numbers were recived? (what configs were compared exactly?) Especially, credits/hour for CPU. It's known fact that multicore (and even in greater degree multicore with HT) CPU performance doesn't scale linearly with CPU cores load. I.e., credit per hour for single task running on 4-core CPU (for example) less (and sometimes much less) than in 4 times less than credit per hour for 4 tasks at once running on 4 cores CPU config. In other words, freeing 1 CPU core one not only speedups (sometimes greatly speedups) GPU, one also speedups remaining CPU tasks as well.
Further, what config allows to run OpenCL NV AP (you compare credits for AP, not CUDA MB here) w/o freeing CPU core? AFAIK good performance possible only in case of 26x.x drivers where CPU freeing not required for NV indeed (though, as Claggy pointed out few times, overall GPU performance with 26x.xx drivers lower than recent drivers + freed core). Where another data published?
SETI apps news
We're not gonna fight them. We're gonna transcend them.
©2019 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.