Latency Measurement (IP/UDP)
The plugin measures RTT and jitter for UDP traffic between client and server agents. The client sends UDP requests, the server returns them, and the client matches responses to requests and calculates latency. Use this scenario to observe changes in network and DUT latency as the load increases.
Add both plugin sides to the task: Client and Server.
The final 16 bytes of the configured payload carry the flow identifier, sequence number, and timestamp. These 16 bytes are part of the specified payload size and overwrite its final bytes, so they do not increase the packet size. The minimum payload size is 16 bytes.
Client settings
| Setting | Description |
|---|---|
| Sources | Client agent, interface, and network that send UDP requests |
| Targets | Destination server agent, interface, and network |
| IP header (L3) | IPv4 or IPv6 settings, including TTL, DSCP, and ECN |
| Payload | UDP payload size and content; the payload is required, and its final 16 bytes are reserved for measurement data |
| Invalid checksum | Send UDP packets with an intentionally invalid checksum |
| Flow count | Number of independent IP address and port pairs; each flow sends requests and receives responses independently |
| PPS per flow | UDP requests per second for each active flow; the aggregate rate equals flow count × PPS per flow |
| Flows per second | Flow activation rate; 0 starts all flows immediately |
| Address distribution | Order in which IP addresses and ports are assigned across flows |
| Source port range | One client UDP port or a range of ports |
| Duration | Plugin runtime |
| CPU cores | Number of cores to use; 0 automatically uses the agent's available resources |
Results are displayed on the Latency Measurement (IP/UDP) dashboard. See Metrics for graph descriptions.