Reviewing shared memory parameters

Overview

During the installation and initial configuration of Testimony, you will have set instance profile parameters on the source system. Once you have performed at least one large recordings in your production system, it is useful to review these settings to see if they need to be increased.

The Force Save Statistics Report

The program /BTI/AUT_FORCE_SAVED_STAT allows you to review a previous recording to see if and when the recording was forced to write directly to the DB rather than to shared memory.

Execute the program in SE38/SA38 on the Central System.

In Plan ID, enter the test plan ID for the recording you are analysing. (You can get this information by displaying the test plan in Configuration —> Test Plans.)
In the “Interval in minutes” field, enter a value of 1. This will show a minute-by-minute breakdown the recording’s forced DB writes.
When you execute the report, you will see output similar to this:

In the image above, you can see that there were several one-minute periods where the number of forced DB writes exceeded the default ALLOWED_DB_WRITES threshold of 1,000. In the case of this recording, the threshold had been set higher so the recording did not abort. However, it does show that there were frequent periods when the shared memory was full, so increasing the relevant shared memory parameters is advisable.