DB2 Purescale Caching Facility Waits Test

In DB2 pureScale, Caching Facility (CF) waits refer to the time a DB2 member spends waiting for the Cluster Caching Facility to respond to a request—typically for locks, page access, or page ownership changes. These waits can impact performance and are important to monitor and analyze.

When a DB2 member needs to read or write a page that it doesn’t own, acquire or release a lock, or invalidate a page in another member’s buffer pool, it must communicate with the CF. The time spent waiting for the CF to process and respond to these requests is called a CF wait.

The DB2 Purescale Caching Facility Waits Test continuously monitors the Purescale cluster , and reports the metrics like -Total command CF requests and Average request wait time.

Target of the test : A DB2 Purescale database cluster.

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the target DB2 Purescale cluster being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	Specify the IP address of the DB2 server in this text box.
Port	Specify the port at which the target host is listening. The default port is 50000.
Username, Password	To monitor Db2 UDB database server, the eG agent should be configured with the credentials of a user with any of the following privileges SYSADM or SYSCTRL or SYSMAINT or SYSMON. Specify the credentials of such a user in the User and Password text boxes. Confirm the Password by retyping it in the Confirm Password text box.
Database	The test uses a database on the monitored Db2 Purescale. Specify the name of the database in the Database text box.
SSL	If the target database server monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No.
Include Available Nodes	In the Include Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.8.136:3306,172.16.8.139:3306
Confirm Password	Confirm the Password by retyping it in the Confirm Password text box.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total command CF requests	Indicates the total number of command requests which have to wait for Caching facility response.	Number	If the number of commands is very high the response time can get longer, it would become matter of concern if the time trends upwards.
Total command CF wait time	Indicates the total time elapsed in waiting for caching facility response.	Seconds
Average request wait time	Indicates the average wait time per command request.	Seconds	If the number of commands is very high the response time can get longer, it would become matter of concern if the time trends upwards.