Message boards : Questions and problems : GPU and CPU mutually exclusive projects
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Nov 10 Posts: 4 ![]() |
I have join 2 projects, one uses only GPU and the other uses only CPU. I have 2 CPU core and 1 GPU. However, the project that uses only GPU completed it computation many many times faster than the CPU and will alway have have to wait for the CPU project to finish, in order to have a "fare share" of "CPU" times. But this isn't the case in my situation, as the GPU only should only be having fare share of GPU with another GPU project, but in my case, only one, then it should run continually, one after another and so as my CPU project. I feel that the CPU and GPU time share (base on Resource share number) between projects should be dependence on the processor type and projects, and not only by projects. Is that a limitation of the BOINC design or is that because I am new to BONIC? Please help. Thanks in advance. :-P |
![]() Send message Joined: 3 Apr 06 Posts: 547 ![]() |
It is indeed a design issue and IIRC something something was changed in the last 6.12.x release(s) concerning this problem. Peter |
Send message Joined: 26 Nov 10 Posts: 4 ![]() |
Thanks Pepo. But I am already using 6.12.6 (x64) and could not find any version higher than this. Is there a later version? Please link me to it. Thanks. Hmmm.... hopefully this feature of "fare-share" base on both process types and projects would be out in the next release, cause we are all wasting too much precious GPU as well as CPU time due to the scheduling algo. :'( |
![]() Send message Joined: 3 Apr 06 Posts: 547 ![]() |
Thanks Pepo. But I am already using 6.12.6 (x64) and could not find any version higher than this. Is there a later version? Please link me to it. Thanks. I think some of the changesets [trac]changeset:22741[/trac], [trac]changeset:22746[/trac] could be related to the problem. 6.12.7 is not yet out, but both [trac]changeset:22767[/trac] (a copy of [trac]changeset:22741[/trac]) and [trac]changeset:22770[/trac] (a copy of [trac]changeset:22746[/trac]) are already prepared inside. And as the changesets were that massively copied from trunk to 6.12 branch yesterday, I'd bet for getting a new version out very soon. Peter |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.