Message boards : GPUs : Separate Resource Shares for GPU?
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Mar 07 Posts: 20 |
I am sure this question may have come up before but I cannot find it. I would like to see separate resource shares on projects for CPU and GPU. Example, I am running Project A on CPU and Project B on GPU. Project A also has GPU work that I am willing to keep my GPU busy while Project B is down. I also have Project C that is CPU that is backup for my Project A but has no GPU work. Under the current Resource Share scheme I cannot run Project A as my GPU backup so I have to have a Project D or let them go cold. |
Send message Joined: 29 Aug 05 Posts: 15565 |
From Separate resource share for GPU? Me wrote: Is it possible to have a separate resource share set up for GPU? |
Send message Joined: 5 Oct 06 Posts: 5129 |
This would be especially useful in the new BOINC v7 range, where work done (effectively the fpops count, expressed as REC) on both CPU and GPU is used in the same calculation for scheduling priority. That means that if a project has both CPU and GPU applications, the work done on GPU effectively means the CPU tasks never run until under deadline pressure. That can be a problem if some applications haven't been ported to GPU, like at Einstein where only one of the three applications has a GPU version - the CPU-only app versions get badly delayed. |
Send message Joined: 15 Mar 07 Posts: 20 |
Another reason I found for this separation. GPU project requires a full CPU, so I have to give it one, no biggie except now CPU project downloads an extra unit that sits in the wings. Most projects this isn't really a problem, but I am doing a project that has long work times and certain benefits for getting projects in quicker. So now it's always holding one maybe for several days which is now going to be sent back at nearly twice it's normal time. There seems to be no way to not have that extra unit sitting there. |
Copyright © 2024 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.