Kernel Trace Usage Notes
When using the Kernel Trace system there are a few basic resource guidelines
to keep in mind.
-
Disk Space - The maxsize
specified when invoking the trace indicates the maximum size (although
it may be smaller if the trace does not run long enough to fill the buffer)
of the trace file to be stored on the local hard drive when the trace session
is stopped. It is recommended that trace files be stored on the disk
volume with the most free space and that they be removed or compressed
once they have been analyzed. Check the amount of free space available
to assure that there will be room to create a trace file of the size desired.
In general, trace files should never be created in excess of 128MB (even
this size may be too large). The Trace Analyzer software generally
will have difficulty loading and using trace files which contain one million
or more records.
-
CPU - Because of the size of trace files, transferring the files
over slower frame relay links will require that the files be compressed
by zipping. In general zip compression is a fairly CPU intensive
process, therefore we recommend that zipping trace files only be done during
off-peak hours.
© 2001 Golden
Code Development Corporation. ALL RIGHTS RESERVED