Difference between revisions of "Condor"

From SourceWiki
Jump to navigation Jump to search
 
Line 19: Line 19:
 
slot1@geog-c200.gg WINNT51    INTEL  Unclaimed Idle    0.000  1662  0+00:00:04
 
slot1@geog-c200.gg WINNT51    INTEL  Unclaimed Idle    0.000  1662  0+00:00:04
 
slot2@geog-c200.gg WINNT51    INTEL  Unclaimed Idle    0.040  1662  0+00:00:00
 
slot2@geog-c200.gg WINNT51    INTEL  Unclaimed Idle    0.040  1662  0+00:00:00
 +
...
 
...
 
...
 
                     Total Owner Claimed Unclaimed Matched Preempting Backfill
 
                     Total Owner Claimed Unclaimed Matched Preempting Backfill
Line 26: Line 27:
 
               Total  191    78    109        4      0          0        0
 
               Total  191    78    109        4      0          0        0
 
</pre>
 
</pre>
 +
 +
Typically you will get several screen's full of output, so I've chopped out the middle part of the listing, leaving just a few at the top and the final summary, given at the end.
 +
 +
From the listing, you can see that the PC called 'GEOG-B224' has someone logged into it, indicated by the keyword '''Owner''', but it is not working hard, as it is '''Idle'''.  In contrast, the PC named 'geog-a105' is marked as '''Claimed''', indicating that it has been grabbed by condor, and it working hard, '''Busy'''.  The third possible state is shown for 'geog-c200', which is not logged into or claimed by condor, i.e. '''Unclaimed''', and is--of course---'''Idle'''.
 +
 +
The final summary tells us that at the time of writing, the pool contains 191 PCs, 78 of which has a user logged in, 109 are claimed by condor and 4 remain unclaimed.
  
 
=Submitting a simple script job=
 
=Submitting a simple script job=

Revision as of 13:05, 22 April 2009

Condor: Making best use of the computers in the teaching labs

Introduction

The Condor Project enables us to run batch jobs on the desktop computers around the department, that would otherwise be standing idle. Condor is particularly useful for high 'throughput' computing, such as an ensemble of independent model simulations, used to evaluate explore parameter-space.

Basic commands

Our 'submission host' is condor.ggy.bris.ac.uk. If you login to that machine, you can review the status of all the machines in the 'condor pool' using the command condor_status:

Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime

slot1@GEOG-B224.gg WINNT51    INTEL  Owner     Idle     0.000  1661  0+01:30:04
slot2@GEOG-B224.gg WINNT51    INTEL  Owner     Idle     0.010  1661  0+01:30:05
slot1@geog-a105.gg WINNT51    INTEL  Claimed   Busy     1.130  1661  0+01:02:57
slot2@geog-a105.gg WINNT51    INTEL  Claimed   Busy     1.130  1661  0+01:02:58
slot1@geog-c200.gg WINNT51    INTEL  Unclaimed Idle     0.000  1662  0+00:00:04
slot2@geog-c200.gg WINNT51    INTEL  Unclaimed Idle     0.040  1662  0+00:00:00
...
...
                     Total Owner Claimed Unclaimed Matched Preempting Backfill

       INTEL/WINNT51   191    78     109         4       0          0        0

               Total   191    78     109         4       0          0        0

Typically you will get several screen's full of output, so I've chopped out the middle part of the listing, leaving just a few at the top and the final summary, given at the end.

From the listing, you can see that the PC called 'GEOG-B224' has someone logged into it, indicated by the keyword Owner, but it is not working hard, as it is Idle. In contrast, the PC named 'geog-a105' is marked as Claimed, indicating that it has been grabbed by condor, and it working hard, Busy. The third possible state is shown for 'geog-c200', which is not logged into or claimed by condor, i.e. Unclaimed, and is--of course---Idle.

The final summary tells us that at the time of writing, the pool contains 191 PCs, 78 of which has a user logged in, 109 are claimed by condor and 4 remain unclaimed.

Submitting a simple script job

Submitting an executable which you have compiled

Running an ensemble of jobs

Condor and energy saving measures