[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Can a "bare-bone" version of condor measure just idle times statistics?
- Date: Tue, 10 Feb 2009 11:29:08 -0500
- From: Jason Stowe <jstowe@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Can a "bare-bone" version of condor measure just idle times statistics?
Installing Condor is the easiest way to test the availability of
nodes. The STARTD is the daemon that will measure the keyboard
idle/busy times. So, in addition to the MASTER, you need a STARTD
running on each of the machines. Additionally, you can set up the
policies that you would use for when to start, suspend, preempt, kill,
etc. jobs to measure machine availability.
For example, the University of Wisconsin policies essentially enable
workstations to participate when they are idle for 15 minutes or more,
suspending when someone uses the keyboard again, and finally
preempting if the keyboard remains busy. Although this may not be
perfect for your environment, you can use these to get a feel for how
idle your machines are by setting the following in your
condor_config.local file on each machine:
WANT_SUSPEND = $(UWCS_WANT_SUSPEND)
WANT_VACATE = $(UWCS_WANT_VACATE)
STARTD_COMPUTE_AVAIL_STATS = True
You can check the exact definitions for these policies in your
condor_config file, and modify them later as appropriate. Once this is
done, you will be able to see machines that are available to run jobs
by typing 'condor_status' and looking for machines in the "Unclaimed"
state. The STARTD_COMPUTE_AVAIL_STATS puts additional information in
your startd classads to assess available time
condor_status -format "%s, " AvailTime -format "%s\n" Name
will show you the AvailTime statistic for your machines.
Jason A. Stowe
Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools
On Tue, Feb 10, 2009 at 9:26 AM, Rob <spamrefuse@xxxxxxxxx> wrote:
> I would like to do some research on idle times of Windows PCs, before
> I launch a full-scale condor project onto the library computer systems.
> Therefore I was wondering how I could just do that, without yet have to
> worry about scheduling, job submission etc.
> Can a stripped version (or 'bare-bone' version) of condor do that for me?
> With "stripped" I mean a minimal number of daemons running on both
> the pool of Windows PCs and the Linux central manager PC.
> For example, would the following do:
> On Windows pool PCs
> DAEMON_LIST = MASTER
> UPDATE_INTERVAL = 60 # use a time resolution of 1 minute
> On Linux central manager
> DAEMON_LIST = COLLECTOR, MASTER
> Could that work?
> I may also have to set appropriate log variables, so that enough info on
> idle time is being logged (I'm not yet at that stage of studying condor).
> All I want, is condor to collect the idle times of all the Windows PCs in the pool.
> I would appreciate if somebody could comment on this idea.
> Thank you!
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: