Experiments with the client simulator using Richard's scenario made it clear that the current scheduling framework (based on STD and LTD for separate processor types) is fatally flawed: it may divide resources among projects in a way that makes no sense and doesn't respect resource shares.
In particular, resource shares, as some have already pointed out, should apply to total work (as measured by credit) rather than to individual processor types. If two projects have equal resource shares, they should ideally have equal RAC, even if that means that one of them gets 100% of a particular processor type. I think it's possible to do this, although there are difficulties due to delayed credit granting. I wrote up a design for this: http://boinc.berkeley.edu/trac/wiki/ClientSchedOctTen Comments are welcome. BTW, the new mechanisms would be significantly simpler than the old ones. This is always a good sign. -- David _______________________________________________ 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.
