[email protected] wrote: > Paul: > > The events that drive rr_sim:
OK, so trying a little KISS: > RPC complete: We have now committed to some more work. Is there anything > that needs to start right now to complete on time. Nope. No need. The request should be reasonable enough and the WUs committed to should be reasonable enough that there should be no change to the presently running work. > File Download Complete: We now have a task ready to run. Does it need to > get started right now? Again, should be no change for the above reasoning. > Task complete: What should we run now. We have a free processor. Yep, but streamline the scheduling to be adding the work to a maintained fifo linked list with a total duration accumulated for the list. Use one variable that is added to and subtracted from. DON'T blindly iterate through the linked list to add it up! DCF is applied to that one variable. That is, the linked list WU times are raw uncorrected times. > Project and Task Suspend: Do we still have the same tasks running? Do we > have an empty resource? Yep. > Project and Task Resume: Some tasks have been suspended for an unknown > amount of time. Do we need to run one of them? Yep. > Please concentrate on the TEST for whether something needs to be run now or > not. Is the problem that of overcomplication in trying to make the scheduler fully preemptive for all transient cases? For the example of the 5 minute deadline WUs, under my suggestions they will never be downloaded because they will be deemed unsuitable for any host that has a "TSI > 2 * WU deadline". For such a project, the project team will have to run their own hosts! Regards, Martin -- -------------------- Martin Lomas m_boincdev ml1 co uk.ddSPAM.dd -------------------- _______________________________________________ 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.
