<!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">
Right, Falkon supports both static and dynamic allocation of resources.
I believe coaster only supports dynamic allocation of resources. We
have lots of information under static allocation, that could help
scheduling, but under dynamic allocation, there is a mixture of known
information (the already allocated resources) and the unknown (the jobs
in the wait queue). In a sense, a smarter scheduler could make use of
at least known information, although this information might frequently
change, and the scheduler would have to adapt frequently.<br>
<br>
Ioan<br>
<br>
Ben Clifford wrote:
<blockquote
cite="mid:Pine.LNX.4.64.0904091528130.25355@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">On Thu, 9 Apr 2009, Ian Foster wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I wanted to point out that when we use Falkon/coasters, we have full control
over scheduling, so in that case we could in principle pre-compute schedules.
</pre>
</blockquote>
<pre wrap=""><!---->
Coasters as they are now are still allocated on an opportunistic basis, so
once we have a coaster stuff could be scheduled to it, but when coaster
workers actually exist is as unknown as when jobs will run in the
non-coaster case, I think.
Where Falkon has been used for pre-allocated resources on machines, with
no dynamic allocation/unallocation, though, the available resources
probably are known well enough for this.
</pre>
<blockquote type="cite">
<pre wrap="">However, in practice we still don't tend to have enough information about
execution times for this to be that useful. At least that's my belief.
</pre>
</blockquote>
<pre wrap=""><!---->
yes.
</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>