[Swift-devel] Try coaster on BG/P ?

Mihael Hategan hategan at mcs.anl.gov
Thu Jun 19 19:10:14 CDT 2008


On Thu, 2008-06-19 at 18:56 -0500, Michael Wilde wrote:

> What Ioan did in Falkon when he went to the multiple-server architecture 
> is relevant here: the client load-shares among all the servers, 
> round-robin, only sending a job to a server when it knows that the 
> server has a free cpu slot. In this way, no queues build up on the 
> servers, and it avoids having a job wait in any server's queue when a 
> free cpu might be available on some other server.
> 

If you have O(1) scheduling, this shouldn't be necessary. It's like
i2u2: Don't build a cluster to reduce the odds of triggering a problem.
Fix the problem instead.




More information about the Swift-devel mailing list