When you select a Session Loading Test, you can define the cycle used to connect and disconnect sessions.
These instructions assume that you are working with a saved test session, and only provide information on defining this test activity. See Related Topics for instructions on configuring the test cases that can use a Session Loading Test.
|
TIP: Start with a test case that you have successfully executed with a Capacity Test. |
To set up a Session Loading Test:
Edit the test case... that will run the test.
Select Session Loading Test from the Test Activity drop-down list, and click the Settings... button.
Determine the values that you want to define for the Session Pending Time... and Session Hold Time..., considering the type of load you want to place on the SUT. A cycle with long hold and pending times can present a peak of activity followed by a lull or a long duration of low to moderate activity. A cycle with short hold and pending times presents a constant mix of connect and disconnect activities. If you check the Ensure Constant Session Loading... box, the values you enter will be validated.
|
TIP: You can configure a test with an evenly balanced load, where sessions are constantly being connected and disconnected, by setting the hold and pending time to half of the time that it takes to establish all of the MN sessions. Example:Example: Assuming that the test connects 100,000 MN sessions (including all contexts or service instances) at a rate of 1,000 sessions/second, 100 seconds are required to connect all of the sessions. When the Session Hold Time and Session Pending Time are 50 seconds, the hold timers in the first sessions start to expire while the remaining 50,000 sessions are being connected. By the time all of the 100,000 sessions have been connected for the first time, the pending timers in the first sessions start to expire, and they begin to be reconnected at the same rate that the later sessions are being disconnected. The result is a balanced session loading cycle with 50,000 active sessions and 50,000 idle sessions at any given time. Every second 1,000 sessions are connected and 1,000 sessions are disconnected. |
In a UMTS test, you can choose the session loading level with the Load Test PDP Contexts Only... checkbox.
Click Apply or OK. If you have entered a value outside of the allowable range you will receive an error.