With the Capacity Test, you can test a system's capacity for simultaneous sessions. The Capacity Test is available in all test cases and access models, and is the default test activity.
The Capacity Test begins establishing sessions at the activation rate that you define. The test system continues to establish sessions until the number of sessions you selected has been reached or until you stop the test. Once the capacity of the SUT has been reached, all subsequent session activation attempts will fail. By setting the requested number of sessions higher than the supported capacity of the SUT, you can determine the actual capacity of the device.
The test system keeps the sessions active for the duration of the test session, or until the test is stopped manually or with Automation Control, and then begins deactivating the sessions at your defined deactivation rate.
When running a Capacity Test against a AAA server, the method of connecting a RADIUS session... can differ depending on the AAA Test you selected. If accounting transactions are included in the test, Interim accounting updates can continue to generate traffic towards the AAA server after an accounting session is successfully established.
NOTE: The disconnect rate only applies to accounting sessions. |
The Data Traffic option can be used in test cases with data traffic capability. Bearer traffic using the data protocol, volume, and rate that you define is transmitted through the established sessions, adding to the real-world activity model.
The SUT Query option can be used to monitor the SUT CPU usage or dynamically adjust the connect and disconnect rates based on the CPU usage.