<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Does a batch-queue prediction service help things in any way?<br>
<a class="moz-txt-link-freetext" href="https://portal.teragrid.org/gridsphere/gridsphere?cid=queue-prediction">https://portal.teragrid.org/gridsphere/gridsphere?cid=queue-prediction</a><br>
<br>
I've always wondered how the Swift scheduler would behave differently
if it had statistical information about queue times. Qin, have you
compared your job replication strategy with one that was cognizant of
the expected wait queue time, in order to meet deadlines? On the
surface, assuming that the batch queue prediction is accurate, it would
seem that scheduling with known queue times might solve the same
deadline cognizant scheduling problem, but without wasting resources by
unnecessary replication. The place where the queue prediction doesn't
help, is when there is a bad node which causes an application to be
slow or fail. In this case, replication is probably the better recourse
to guarantee meeting deadlines.<br>
<br>
Here is their latest paper on this:
<a class="moz-txt-link-freetext" href="http://www.springerlink.com/content/7552901360631246/fulltext.pdf">http://www.springerlink.com/content/7552901360631246/fulltext.pdf</a>. The
system is deployed on the TeraGrid, and has been for a few years now.
As far as I have heard, it is quite robust and accurate.<br>
<br>
Cheers,<br>
Ioan<br>
<br>
Ben Clifford wrote:
<blockquote
cite="mid:Pine.LNX.4.64.0904081505050.25355@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">On Wed, 8 Apr 2009, Mihael Hategan wrote:
This:
</pre>
<blockquote type="cite">
<pre wrap="">planning the whole workflow buys us little in a (very) dynamic
environment in which submitting a job one minute later may mean the
difference between 1 minute of queue time and one hour of queue time
</pre>
</blockquote>
<pre wrap=""><!---->
and this:
</pre>
<blockquote type="cite">
<pre wrap="">You need some SLA/QOS to address that.
</pre>
</blockquote>
<pre wrap=""><!---->
seem to be significant characteristics that make the environments we run
on not amenable to scheduling in the traditional sense. The lack of any
meaningful guarantees about almost anything time-related makes everything
basically opportunistic rather than scheduled.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
===================================================
Ioan Raicu, Ph.D.
===================================================
Distributed Systems Laboratory
Computer Science Department
University of Chicago
1100 E. 58th Street, Ryerson Hall
Chicago, IL 60637
===================================================
Email: <a class="moz-txt-link-abbreviated" href="mailto:iraicu@cs.uchicago.edu">iraicu@cs.uchicago.edu</a>
Web: <a class="moz-txt-link-freetext" href="http://www.cs.uchicago.edu/~iraicu">http://www.cs.uchicago.edu/~iraicu</a>
<a class="moz-txt-link-freetext" href="http://dev.globus.org/wiki/Incubator/Falkon">http://dev.globus.org/wiki/Incubator/Falkon</a>
<a class="moz-txt-link-freetext" href="http://dsl-wiki.cs.uchicago.edu/index.php/Main_Page">http://dsl-wiki.cs.uchicago.edu/index.php/Main_Page</a>
===================================================
===================================================
</pre>
</body>
</html>