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

RE: [Condor-users] meaning of condor_stats output



Many thanks, that is _much_ clearer now. The stats do seem be updated
OK when I run jobs and I'm only using a single pool. As a final
question -- is it possible to indentify individual jobs to get a
break down on how long each ran for. I can't see this info in the
raw history data.

-ian.

--On 10 August 2004 11:20 +0100 Matt Hope <Matt.Hope@xxxxxxxx> wrote:

this indicates that, for the local pool, at the specified times the
specified user had 0 running jobs and 1 queued job.

without a time period I believe it defaults to last hour.

1) do you have multiple pools (even unintentionally)?

2) are you getting stats in a useful time period (i.e. change the time
period or run it while the jobs are running)

if you had 3 jobs and 2 machines you might get output like (comments
prefiixed by #)...

1092043363      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    0       0
# submitted your jobs
1092043604      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    0       3
1092043844      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    0       3
# 1 st job starts
1092044084      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    1       2
# 2 nd job starts
1092044190      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    2       1
# 1 st job finishes
1092045060      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    1       1
# 3 rd job starts
1092056011      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    2       0
1092057300      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    2       0
# 3 rd job finishes
1092058760      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    1       0
# 2 nd job finishes
1092059720      civsp@xxxxxxxxx/coastalre02.liv.ac.uk   :    0       0

You may find that steps get missed (if changes happen within timescales
smaller than the sampling period)

Essentially it is providing snapshots of (a very restricted view of)
state at the particular time...

the orgformat lets you see precise time, the percentage view makes
graphing and other visual representations easier to do from scripts
(though you could achieve the same effect and more without too much
effort if you were parsing the output yourself with a full featured
language)

Matt

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Dr Ian C. Smith
Sent: 10 August 2004 10:58
To: Condor-Users Mail List
Subject: RE: [Condor-users] meaning of condor_stats output


stats on users


-ian.

--On 10 August 2004 10:44 +0100 Matt Hope <Matt.Hope@xxxxxxxx> wrote:

> 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.
> *****************************************************************
>
> _______________________________________________
> 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

_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users