<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Times">Ben:</font></div><div><font class="Apple-style-span" face="Times"><br></font></div><div><font class="Apple-style-span" face="Times">You may recall the work that was done by Greg Maleciwz (sp?) on prioritizing jobs that enable new jobs to run. Those ideas seem relevant here.</font></div><div><font class="Apple-style-span" face="Times"><br></font></div><div><font class="Apple-style-span" face="Times">I met last week with a smart fellow in Singapore, Qin Zheng (CCed here), who has been working on the scheduling of replicant jobs. His interest is in doing this for jobs that have failed, while I think your interest is in scheduling for jobs that may have failed--a somewhat different thing. But there may be a connection.</font></div><div><font class="Apple-style-span" face="Times"><br></font></div><div><font class="Apple-style-span" face="Times">Ian.</font></div><div><br></div><br><div><div>On Apr 6, 2009, at 9:39 AM, Ben Clifford wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>even more rambling... in the context of a scheduler that is doing things <br>like prioritising jobs based on more than the order that Swift happened to <br>submit them (hopefully I will have a student for this in the summer), I <br>think a replicant job should be pushed toward later execution rather than <br>earlier execution to reduce the number of replicant jobs in the system at <br>any one time.<br><br>This is because I suspect (though I have gathered no numerical evidence) <br>that given the choice between submitting a fresh job and a replicant job <br>(making up terminology here too... mmm), it is almost always better to <br>submit the fresh job. Either we end up submitting the replicant job <br>eventually (in which case we are no worse off than if we submitted the <br>replicant first and then a fresh job); or by delaying the replicant job we <br>give that replicant's original a chance to start running and thus do not <br>discard our precious time-and-load-dollars that we have already spent on <br>queueing that replicant's original.<br><br>--<br><br>_______________________________________________<br>Swift-devel mailing list<br><a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel<br></div></blockquote></div><br></body></html>