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

RE: [Condor-users] meaning of condor_stats output



are you attempting to determine stats on *jobs* or on users.

condor_stats seems designed for the latter...

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Dr Ian C. Smith
> Sent: 10 August 2004 10:27
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] meaning of condor_stats output
> 
> 
> Hi Alain,
> 
> I'm still totally confused as to how to interpret this. Say I have
> submitted three condor jobs during the period in question, which
> run for  tr1, tr2 and tr3 seconds and are idle for ti1, ti2 and ti3
> seconds how might this appear using -orgformat. An example of 
> my -orgformat
> output looks like
> 
> 
> > 1092043363      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :   
>     0       1
> > 1092043604      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :   
>     0       1
> > 1092043844      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :   
>     0       1
> > 1092044084      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :   
>     0       1
> [snip]
> 
> I'd like to create a script to produce usage reports. Is condor_stats
> the best way of doing this or would I need to parse the history files
> myself (is the format of these documented anywhere).
> 
> thanks,
> 
> -ian.
> 
> 
> --On 09 August 2004 09:47 -0700 Alain Roy <roy@xxxxxxxxxxx> wrote:
> 
> >
> >> Can anyone explain what the output of condor_stats indicates.
> >
> > The manual page is confusing, but I think that all of the 
> information is
> > there--I apologize for the confusing text.
> >
> > The output is terse because it is meant for input into a 
> script that can
> > turn the data into pretty graphs. Probably we should make a verbose
> > option.
> >
> >> I've had a read of the man pages but I still can't work
> >> it out. For example what does this mean:
> >>
> >> $ /opt/condor/bin/condor_stats   -userquery
> >> tcadmin2@xxxxxxxxx/239032-mstc22.liv.ac.uk
> >> 96.62   1       0
> >> 96.90   1       0
> >> 97.17   0       0
> >> 97.45   0       0
> >> 97.73   0       0
> >> 98.01   0       0
> >> 98.28   0       0
> >
> > I assume that's a subset of the data. You should have 
> numbers ranging
> > from close to zero to close to 100 in the first column.
> >
> > First column:
> >
> >> The first column always represents the time, as a percentage of the
> >> range  of the query. Thus the first entry will have a 
> value close to
> >> 0.0, while  the last will be close to 100.0. If the 
> -orgformat option is
> >> used, the  time is displayed as number of seconds since 
> the Unix epoch.
> >> The  information in the remainder of the columns depends 
> on the query
> >> type.
> >
> > You may find it easier to interpret with the -orgformat argument.
> >
> > Next two columns:
> >
> >> The information displayed includes the number of running 
> jobs and the
> >> number of idle jobs.
> >
> > So you have:
> >
> > time running-jobs idle-jobs
> >
> > -alain
> >
> >
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 


*****************************************************************
Gloucester Research Limited believes the information 
provided herein is reliable. While every care has been 
taken to ensure accuracy, the information is furnished 
to the recipients with no warranty as to the completeness 
and accuracy of its contents and on condition that any 
errors or omissions shall not be made the basis for any 
claim, demand or cause for action.
*****************************************************************