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.
