SarCheck is an inexpensive tool developed to help system administrators with UNIX performance tuning. It does this by analyzing the output of sar, ps, and
other tools, and then reading more information from the kernel. It then identifies problem areas, and if necessary, recommends changes to the system's tunable parameters.
SarCheck translates your system's sar reports into a Plain English report and will insert HTML tags into the text if you want to view the output through a browser.

SarCheck was first made introduced by Aurora Software Inc. in 1994 and it is a mature, stable product which continues to be enhanced. From the very beginning we've concentrated on giving you answers in plain English.

SarCheck can detect CPU Bottlenecks, runaway processes, I/O bottlenecks, improper I/O load balancing, slow disk devices, memory bottlenecks and leaks, inefficient system buffer cache sizing, improper system table sizes, and inefficient PATH variables.
The resource analysis and recommendations sections of SarCheck will analyze the data and make recommendations for gradual changes to your system.

The capacity planning component of SarCheck will approximate the amount of capacity left on your system and determine which resource is likely to become exhausted first. SarCheck is available for most systems running Solaris SPARC 2.5+, HP-UX 10.10+, AIX 4.2+, OpenServer Release 5, and UnixWare 7 .

Check the appropriate FAQ or contact us if you have any questions.

The philosophy behind our development of SarCheck can be seen at this web site. Note the lack of huge garish graphics, the high ratio of content to "fluff", and the frequent updates.
SarCheck gives you real information so that you can make real decisions about how to improve UNIX performance.
This is not one of those tools which produce graphs that you have to interpret for yourself, and it certainly won't encourage you to press a button to automatically change 60 things at once.

SarCheck trivia:
SarCheck has been licensed and installed by Universities, Government agencies, and lots of companies around the world. The northernmost licensee is located in
Tallinn, Estonia and the site of the southernmost licensee is in Wellington, New Zealand. The licensee located farthest from our office in the northeast corner of the U.S. is in Perth, Australia.

Requirements:
(SarCheck resource utilization is trivial. If your system can't spare the resources needed to run SarCheck, it has big problems)

SarCheck only requires about 0.3 megabytes of disk space. Report files containing sar and ps data will take up additional space, and you control how much of this data you want to keep.
SarCheck typically uses less than one second of CPU time per day on Pentium SCO systems and all but the slowest HP 9000 and Solaris SPARC systems.
An SCO 3.2v4.2 system with a 486/33 CPU used two seconds of CPU to analyze and consolidate 10 hours of sar and ps -elf data.
That is a worst case and works out to a mere 0.006% CPU overhead during the 10 hour period. CPU usage by SarCheck is typically less than 0.5 seconds.
SarCheck requires about one megabyte of memory for the few seconds that it's running. This varies based on operating system and the problems detected by SarCheck when it's running.

As an example of how little memory is needed by SarCheck, it runs well on 4 megabyte SCO UNIX 3.2v4.2 systems!