Estimating Transactions-per-Second

Your dsTest license limits the maximum Transactions-per-Second (TPS) achievable, and if you're using one of the floating license options the licensed TPS is shared among all instances of dsTest tied to that license. dsTest will consume licensed TPS in one of two ways. It will either check out the TPS you specify when you launch dsTest, which will remain checked out until dsTest is terminated, or it will dynamically check out the TPS requested within the test configuration when the test is loaded and then release the TPS when the test is unloaded.

If there is contention for licensed resources, you can most efficiently utilize those resources by checking out only the TPS required for current activities. In some cases it makes more sense to check out TPS when dsTest is launched - when it will be dedicated to either automated long duration high-TPS performance tests or automated low-TPS functional testing, for example. Conversely, instances that are used for test development, troubleshooting, or intermittent testing would consume less license resources if they use the dynamic model.

Interface Application TPS

dsTest considers one application layer request/response exchange using any Control Plane protocol to be a transaction. One application procedure, therefore, may require multiple transactions. The Control Plane TPS your test will attempt to achieve depends on the number of concurrent actions, their rates, and the number of subscribers involved. In the configuration of each interface application you can specify the expected TPS and thereby inform dsTest of the TPS required for that application. If you plan to dynamically check out license resources you must configure the expected TPS for each application.

Non-IP data transmitted over NAS and all REST traffic are considered to be Control Plane traffic when calculating TPS.

You can determine the actual aggregate TPS generated by your test by monitoring the Current Transaction Rate measurement. You'll find it under Detail Measurements > diag in a dsClient Desktop chart or tabular report, or you can query it with dsClient Terminal via the diag om command which will display the TPS for the current report interval. If your test utilizes multiple interface applications, you can see TPS per application by using dsClient Desktop's SmartReport and selecting By Application Type > All from the Application Transactions/Second summary chart's menu.

Data Traffic TPS

dsTest calculates TPS for data traffic based on Packets per Second (PPS) according to the table below. For example, 500 PPS with Basic Data equates to 5 TPS while 500 PPS with SIP equates to 250 TPS. TCP control packets and data packets without payload are not counted in PPS.


Traffic Type


GTP-U SmartFlow


Data Verification


Basic Data over User Plane


Pass-Thru Data