FairCom Server configuration options provide an easy way to enable automatic performance snapshots. Additional flexibility and access to the complete set of statistics maintained by the FairCom Server is available programmatically through the SnapShot c-tree API function. This API function:
Tips for Performance Monitoring with SnapShot
The SnapShot API provides a wealth of detailed information concerning may aspects of the system. The following system counters (ctGSMS) are particularly useful for overall performance monitoring.
The ISAM counters provide a good indication of how much work is being requested (unless there are lots of low-level API calls in your application). Higher level APIs, such as c-treeDB and SQL, are also reflected here.
Current lock counts
The current lock counts show the lock contention at any given instant. Similar counters are available with cumulative counts.
The cache counters are a good indication of how much CPU work c-tree is doing. A single ISAM record search by key must find several index cache pages and at least one data cache page. Likewise, an ISAM add must find at least 1 data cache page and at least 1 index cache page per associated index. requests - hits = cache misses, which means that system I/O call(s) were needed.
For the indices, these only counts cache searches (locating the desired cache page). Some operations (NextKey or NextRecord) can sometimes skip the cache search.
System I/O counters
These following counters monitor the overall system I/O. In the default configuration, I/O on the data and index files is cached by the file system, so you have to look at the system to get real I/O information (various keywords affect this behavior).
The following counters give a good idea of transaction activity:
The log writes default (with COMPATIBILITY LOG_WRITETHRU) to real disk I/O requests by the system.