----- Original Message -----
From: "Thomas Kern" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, November 07, 2005 4:34 PM
Subject: VM Performance Tool Kit questions
I have just begun to work with the VM Performance Tool Kit and I have a few
questions for the group.
I have turned on BENCHMRK for a particular user (MISPROD) with and without
a FILE option in the FCONX $PROFILE. I have USERLOG MISPROD in the FCONX
REPORTS file. My report always shows approximately the last 120 entries
for
this user, not the whole day's worth of data. I know that the MISPROD
USERLOG file is a copy of all of the data, but I don't want to have to
reformat it and print it seperately from the regular report.
Performance Toolkit will keep, by default, the last 120 lines of each 'by
time' log
in its work space. For the default monitor sample interval of 60 seconds
this results
in having only the last two hours' worth of data available for viewing:
usually ok
for realtime performance analysis, but definitely not enough if you want to
save
history data.
There are two ways to change things in PerfKit so as to retain data for
longer periods:
a) Include the command 'FC MONCOLL REDISP nnn' in your FCONX $PROFILE
where 'nnn' specifies the number of lines that should be kept (max.
value is 720).
This setting applies to ALL of the 'by time' logs, but it MUST be
included in the
initialization file FCONX $PROFILE to become effective.
b) Issue the command 'FC SET BYTIME nn' to indicate that each line of the
general
'by time' logs should display not only the value for a single monitor
sample interval,
but the average for periods of 'nn' minutes each.
This setting can be changed while PerfKit is up and running, but it does
NOT
apply to any of the benchmark files. (The reason for implementing it
this way
was that I intended benchmarking to be activated only for the analysis
of performance
problems: you would then want to see as much detail as possible, and
averages
for longer periods of time very often aren't good enough.)
So, to keep data for longer periods of time in the 'by time' reports, you
may use
a combination of a) and b). For the benchmark logs, only a) will help as far
as the
printed reports are concerned but, as you've seen, using the 'FILE' argument
you can
have all of the data written to disk.
I have not tried to use PERFKIT as a PROP replacement in my OPERATOR or
other service machines yet. Does anyone have a working FCONX $PROFILE for
such a server that isn't doing the real-time monitoring?
The section 'Special Line Processing' in chapter 2 of the documentation
gives some
examples of things you could do, and how to do them. Just start with an
empty
FCONX $PROFILE if you want to run PerfKit without activating performance
monitoring:
the majority of the specifications in the sample file that are not related
to realtime
monitoring are just duplicating the default settings anyway, they were
included just
as placeholders to allow easily changing things a user might want to modify.
Eginhard Jaeger
