Rob, no apology necessary and I hope I did not come across as wanting to
start or play in a 'mine vs yours' game or make readers think that.
While it is true that the history data files do not contain the same
detail as raw mondata, they are worthwhile to review and investigate if
one is not f
On Nov 9, 2007 9:34 PM, Roger Lunsford <[EMAIL PROTECTED]> wrote:
> The PERFKIT can create HISTORY DATA files, which can be looked at
> as "condensed monitor data" files. The PERFKIT can also process these
That's not really the same. Those are just a small set of (system
wide) metrics that are k
The PERFKIT can create HISTORY DATA files, which can be looked at
as "condensed monitor data" files. The PERFKIT can also process these
data files via the PERFKIT MENU OPTION 32 HISTORY DATA FILES. Within the
ACUM HISTSUM and the MMDD HISTLOG I can see the CPU Utilization on
each monitor
On Nov 8, 2007 8:22 AM, Jeff Gribbin, EDS <[EMAIL PROTECTED]> wrote:
> Regarding the, "problem" of perhaps wishing to only collect a subset of
> the monitor records for, "MONWRITE" / post-processing activities while
> still needing a fuller set of records for realtime monitoring, it is
> really a
Regarding the, "problem" of perhaps wishing to only collect a subset of
the monitor records for, "MONWRITE" / post-processing activities while
still needing a fuller set of records for realtime monitoring, it is
really a trivial exercise to write a PIPE that collects MONITOR records (
a
la MO
day, November 01, 2007 3:01 PM
Subject: Controlling MONWRITE and the size of its 191 disk
Hello,
I'm using Performance toolkit and would like to use the batch interface.
I've set up the Performance toolkit batch commands however my problem now is
the MONITOR DATA file.
Subject: Re: Controlling MONWRITE and the size of its 191 disk
On 11/1/07, Hamilton, Brian <[EMAIL PROTECTED]> wrote:
> The size of the file grows quickly, it about 1 hour the file consumes
90
> cyls
You're right. Raw data files are huge. One option is to make the
interval
On 11/1/07, Hamilton, Brian <[EMAIL PROTECTED]> wrote:
> The size of the file grows quickly, it about 1 hour the file consumes 90
> cyls….
You're right. Raw data files are huge. One option is to make the
interval larger, but this also very much limits the detail you can see
in your real time data
Hello,
I'm using Performance toolkit and would like to use the batch interface.
I've set up the Performance toolkit batch commands however my problem
now is the MONITOR DATA file.
The size of the file grows quickly, it about 1 hour the file consumes 90
cyls
My goal is to collect th
