This is an analysis of the data contained in the file /tmp/rpt. The data was collected on 05/29/1998, from 09:34:48 to 16:40:00, from system 'scosysv'. There were 22 sar data records used to produce this analysis. Operating system is SCO OpenServer Release 3.2v5.0.0. 1 processor is present. 32 megabytes of memory are present.
Average CPU utilization was only 0.4 percent. This indicates that spare capacity exists within the CPU. If any performance problems were seen during the monitoring period, they were not caused by a lack of CPU power.
The run queue had an average depth of 1.7. This indicates that there was not likely to be a performance problem caused by processes waiting for the CPU.
The CPU was idle (neither busy nor waiting for I/O) and apparently had nothing to do an average of 98.8 percent of the time. If overall performance was good, this means that on average, the CPU was lightly loaded. If performance was generally unacceptable, the bottleneck may have been caused by remote file I/O which cannot be directly measured with sar and cannot be considered by SarCheck UltraLite.
The average cache hit ratio of logical reads was only 83.7 percent. Tuning the buffer cache size is unlikely to help because disk activity was so light.
In the event of a system crash, an average of 20 seconds worth of data will be lost because it will not have been written to disk. This is controlled by the NAUTOUP and BDFLUSHR parameters. This statistic has been calculated using the formula: NAUTOUP + (BDFLUSHR / 2).
The ratio of exec to fork system calls was 1.03. This indicates that PATH variables are efficient.
The percentage of HT namei cache hits was an acceptable 91.9 percent. Note that namei caching is only performed when the length of directory and filenames are 14 characters or less. For best performance, pathname components should be less than 15 characters long.
No evidence of a memory shortage was seen in the following statistics: The swap queue was occupied an average of 0 percent of the time. The average rate at which the page stealer and/or swapper daemons have reclaimed pages of memory was 0.0 per second. The average swap out transfer request rate was 0.0 per second.
The amount of freeswp did not change during the monitoring period, indicating that the system has plenty of memory installed.
The average number of free pages reported by sar was significantly higher than the value of GPGSHI, confirming that the system is not chronically short of memory.
The value of MAXUP is 100 and the maximum grown size of the process table as reported by sar was 95.
The device Sdsk-0 was busy an average of 1.6 percent of the time and had an average queue depth of 2.5 (when occupied). This indicates that the device is not a performance bottleneck. The average service time reported for this device and its accompanying disk subsystem was 29.4 milliseconds. This is very slow by modern standards, and the poor performance may due to either the disk, the location of multiple filesystems on the disk, or the disk controller. Service time is the delay between the time a request was sent to a device and the time that the device signaled completion of the request.
More information on performance analysis and tuning can be found in the SCO OpenServer(TM) Performance Guide, which is part of the SCO OpenServer Release 5 documentation set.
Please note: In no event can Aurora Software Inc. be held responsible for any damages, including incidental or consequent damages, in connection with or arising out of the use or inability to use this software. All trademarks belong to their respective owners. Code version: 3.61. Build ID: skunk-98.
Thank you for using SarCheck UltraLite. To order a licensed copy of the full version of SarCheck, type '/usr/local/bin/ulite -o' at the prompt to produce the order form, and follow the instructions. More information is available at http://www.sarcheck.com.
(c) copyright 1994-1998 by Aurora Software Inc.