1.1. Testing Performance¶
This document describes how to run a combined latency and throughput test application for RTI Connext DDS.
The test measures what is sometimes called loaded latency -- latency at a given throughput level. It can help you answer questions such as:
For a given publishing configuration (e.g., queue size, batching settings), sample size, and subscribing configuration (e.g., queue size, Listener vs. WaitSet), what is the throughput of my network?
When my network is heavily loaded, what latency can I expect?
For a given configuration, what is the best-case latency with no other traffic on the network?
For examples of specific configurations, see the Command-Line Parameters examples section.
This performance test is implemented in C++ (Traditional and Modern APIs), C# and Java.
Note: All references in this document to “C++” refer to both the Traditional and Modern C++ APIs unless otherwise noted.
RTI Perftest can be built against RTI Connext DDS Professional and RTI Connext DDS Micro 3.0.0 (also 2.4.11 with some limitations).
RTI Perftest can also be used to test raw
To do this, RTI Perftest uses the RTI Connext DDS Professional internal
transport layer to interact with sockets. In this mode, RTI Perftest skips
the DDS protocol to directly send the data, which is serialized using the same
functions that RTI Connext DDS Professional uses.
The publishing side of the test writes data as fast as it can. Every few
samples (configured through the command line), it sends a special sample
requesting an echo from the subscribing side. It uses this
request -> echo exchange to measure round-trip latency (RTT). Then, the
one-way latency is calculated as RTT/2.
As you will see in Command-Line Parameters section, there are several command-line options, including ones to designate whether the application will act as the publisher or subscriber.
You will start multiple copies of the application (typically 1 publisher and 1 or more subscribers):
The publishing application publishes throughput data; it also subscribes to the latency echoes.
The subscribing applications subscribe to the throughput data, in which the echo requests are embedded; they also publish the latency echoes.
The publisher prints the latency test results meanwhile the subscriber prints the throughput results.
1.4. Latency Test vs Throughput Test¶
RTI Perftest allows 2 operational modes: Throughput Test and Latency Test.
1.4.1. Throughput Test¶
The throughput test is the default mode when RTI Perftest publisher and subscriber applications are started.
In this mode, the publisher side starts sending samples as fast as possible. Once every latencyCount samples (which for a throughput test is 10000 samples by default), RTI Perftest marks the sample so it is answered by the subscriber side. The answer is the exact same sample. Therefore, based on the time the sample was sent and the time the publisher receives it, the Round-Trip Time (RTT) can be calculated.
Doing a throughput test provides the maximum throughput (Mbps) at which the publisher will be able to send samples to a subscriber. The latency obtained in this test will also be displayed by the publisher application; however, that latency is affected by the fact that the Publisher and Subscriber will be flooding the network and filling all their internal queues (sending and receiver queues, as well as the Nic queues). Therefore, for measuring the pure latency in the best-case scenario, the Latency Test mode should be used.
1.4.2. Latency Test¶
In this mode, the publisher side changes its behavior: every sample it sends
is marked as a latency sample (
LatencyCount is equal to 1 in this case).
The Publisher also waits until the sample is sent back and received by the Publisher
before sending the next sample (called
stop-and-wait mode or
This way, the latency test mode is able to send samples, ensuring all the RTI Connext DDS queues will be empty.
The only requirement to change the operation mode to do a latency test is to
-latencyTest command-line parameter to the publisher side. See the
Command-Line Parameters section for more details.