My previous email points out that no policy is both efficient and optimal, but that certainly doesn't mean the current policies can't be improved a bit. For example:
- a non-EDF multi-CPU job should not be moved ahead of an EDF 1-CPU job if there are enough other 1-CPU jobs to fill the CPUs. - use least slack time first or some other policy to schedule jobs that miss deadlines under RR. (there are a numbers of policies that do better than EDF on average). - use intelligence (e.g., least slack time first) in ordering the execution of a group of jobs that arrive simultaneously (Richard H's AQUA example). I'd prefer to not add a 2nd simulator (EDF) to the client unless it's really clear that it's needed. Anyway: we're unlikely to make any of these changes for a couple of months; things like the credit system have priority. If anyone wants to implement these or other changes, and prove using the client simulator that they improve things, we could incorporate them. -- 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.
