Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.sys.isis
Subject: Re: roll your own supercomputer
Message-ID: <2853@uakari.primate.wisc.edu>
Date: 31 Jul 90 15:52:07 GMT
References: <43872@cornell.UUCP>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Distribution: comp
Lines: 20

From article <43872@cornell.UUCP>, by ken@gvax.cs.cornell.edu (Ken Birman):
> 
> My feeling is that Condor makes a lot of assumptions about why people
> are trying to manage the resources in their machine and what it means
> to schedule a task.  Although quite nice for the simulation work being
> done at Wisconsin, many applications would have problems with IO performance
> degradations factors of 2-3, and the Condor concept of job checkpointing
> is also very specific to the type of jobs Wisconsin is running on the
> system.  Also, I have the impression that Condor isn't very fault-tolerant,
> but I could be out of touch with the most recent  release of this 
> system.

Mostly correct.  Recently the CS department moved a lot of its machines
from one building to another.  Condor jobs that were started before the
move resumed and completed after the moved.  (I don't know if this involved
movement of the Condor admin machines or not.  If so, this is that much
more impressive.)

Paul DuBois
dubois@primate.wisc.edu