[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Clipped Mac OSX

We have a somewhat similar situation:  Windows SMP machines with jobs
that can run up to several days.  We want minimal impact on interactive
use, so if both CPUs on the SMP machines are in use and the keyboard is
in use, we suspend one of the Condor jobs for up to a few hours total
time.  It seems to work well: The suspense occurs immediately on
keyboard use, then unsuspends after a period of no keyboard use (5
minutes).  Condor keeps track of total suspend time, and if a job
accumulates beyond a max we no longer suspend it (so it doesn't delay an
entire batch of runs).

If your jobs are evicted for a similar reason (interactive use) you
might want to consider suspending rather than evicting.  Evicting just
doesn't make much sense with jobs that run more than an hour or two.

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Seth Price
Sent: Tuesday, June 05, 2007 12:40 PM
To: Condor-users@xxxxxxxxxxx
Subject: [Condor-users] Clipped Mac OSX

I'm with the SAGE group on the wisc campus (www.sage.wisc.edu). We  
have a cluster of 40 Mac G5 processors, and we are considering adding  
a number of 8 core Mac Pros to the mix.

Are there plans for un-clipping the Mac version of Condor? We would  
really like checkpointing to work.

The largest complaint with the condor setup is when a job gets  
evicted for one reason or another, and the run needs to start from  
scratch on another machine. The scientists I'm working with often  
have week-long jobs, so this is a serious problem.

We might abandon using condor in favor of stand alone machines to put  
fewer possible interruptions between the scientists and the hardware.  
(I hope not, though. I'm sure I have things configured correctly this  


PS: I realize I can configure condor to *never* evict a job, but my  
intent is to only evict my 'nice' jobs whenever any other jobs are