|
|
|
The FairCom DB Performance Snapshot capability enables the capture of performance monitoring data using a combination of configuration file options and calls to the SnapShot() function. The performance data can be captured automatically at specified intervals or on demand.
Performance data maintained and made available by the server’s snapshot capability includes the following: File lock statistics, transaction time histogram, transaction commit delay statistics, transaction log I/O, function timings, data and index cache details, disk read and write statistics, and communication read and write statistics.
FairCom DB supports the snapshot capability on systems that support 8-byte integers. On systems that do not support a high-resolution timer, some aspects of the snapshot are not available.
|
|
|
Server configuration file options can be used to capture automatic system snapshot data.
When SNAPSHOT_INTERVAL <interval in minutes> is specified in the server configuration file, an automatic snapshot thread performs a system snapshot after each interval. The automatic system snapshot is written to FairCom DB’s system event log (SYSLOG) files.
The following configuration entries can be used multiple times to include snapshot details to for users and files in the snapshot output. Use a pattern of ‘*’ to activate monitoring for all user ID’s or files.
SNAPSHOT_USERID <user ID>
SNAPSHOT_FILENAME <file name>
Specifying DIAGNOSTICS SNAPSHOT_SHUTDOWN in the server configuration file causes the server to log system snapshot details to the file SNAPSHOT.FCS when the server shuts down.
|
|
|
The SnapShot() API function can be used to control automatic snapshots, overriding configuration options (if any), and can capture on-demand server performance data to the SYSLOG files, to the human-readable SNAPSHOT.FCS file, or as a return to the calling program. See the FairCom DB Function Reference Guide for full details on using the SnapShot() API function.
