[Swift-devel] Re: swift-falkon problem... plots to explain plateaus...

[Ioan Raicu]

Ben Clifford wrote:
> On Mon, 24 Mar 2008, Ioan Raicu wrote:
>
>   
>> start completing, and new ones get dispatched.  At around 132 seconds, the
>> wait queue is empty, and some workers start becoming idle (the red area)... by
>>     
>
> Ideally swift would be keeping the queue full until there is nothing left 
> to send. There shouldn't be two distinct 600 and 400 job bursts. But I 
> guess that may be because the job throttling isn't set to a large enough 
> infinity.
>   
Its not the throttling... Swift sent all 1000 tasks at once (all within 
the first 10 seconds).  There were 600 workers running on 600 CPUs, so 
600 (of the 1000) tasks went from the wait queue to the running state, 
and there were 400 tasks left in the wait queue.  After some time, the 
first round of tasks (the first 600) completed and the second round of 
tasks (400) went from the wait queue to the running state.  So, the two 
distinct rounds, 600 then 400 is because of the 600 CPUs and 1000 total 
tasks...

Ioan


-- 
===================================================
Ioan Raicu
Ph.D. Candidate
===================================================
Distributed Systems Laboratory
Computer Science Department
University of Chicago
1100 E. 58th Street, Ryerson Hall
Chicago, IL 60637
===================================================
Email: iraicu at cs.uchicago.edu
Web:   http://www.cs.uchicago.edu/~iraicu
http://dev.globus.org/wiki/Incubator/Falkon
http://dsl-wiki.cs.uchicago.edu/index.php/Main_Page
===================================================
===================================================


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20080324/4bfe6e89/attachment.html>