The new system (see updated doc: http://boinc.berkeley.edu/trac/wiki/CreditNew) will have separate quotas and error rates per resource type (CPU, NVIDIA, ATI).
Maintaining these separately for each GPU would require modeling multiple GPUs separately, rather than as N instances of the same thing as is currently done. This would be a sweeping change, and won't get done in the near term. -- David Raistmer wrote: > If hosts' task quota computed in old way, host that does valid CPU > computations but invalid GPU ones will pollute database and waste project > resource indefinitely. > GPU usually much faster than CPU so many invalid tasks can be returned per > single valid one. > Moreover, even if CPU/GPU quota separation will be introducted, there are > still multi GPU hosts that can pollute database with even bigger rate doing > correct computations on one GPU and invalid ones on anothers. > Current quota system applicable only to single host-single device approach > and apparently should be changed. > Right now I have no good idea what replacement can be, but this question > definitely deserves consideration. > > One possible solution could be to track good/bad results ratio per hardvare > device (not per host) and inhibit work fetch for whole host if one of its > devices has too bad good/bad ratio. Or issue some instruction to BOINC > client to block affected device from reciving work (it could be more > graceful approach). > More ideas? > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
