Here are the steps to do a CPS(Connect per second) testing.
- Create HTTP GET scenario
- Set Total Connections in Connection Establishment
- Set Ramp-Up, Steady, Ramp-down duration accordingly
- Set Connection Updates->Connection Rebirth to “With same Src IP”
- Set Connection Updates->Repetitions to 0 or simply delete it.
- The screenshot below gives you 200K CPS
- Go to Scenario->Behavior->Connection closed by, set to Client
- Add a live chart of TCP State > Established to monitored the TCP CC
- Add a live chart of TCP State Rate > Established to monitor the TCP CPS
The test above will do:
- Client establishes a TCP connection with a server.
- Client sends a request to the server
- Server replies a response to the client
- Client immediately closes down the TCP connection
- As soon as the TCP connection is closed, another one is created (go back to A)
If two test ports are back-to-back connected, the TCP CC is close to 0. TCP CC is a result of the latency introduced by the DUT between the test ports. I’ve attached a simple PDF doc to show a test result carried out on our Fortigate DUT.