2.4.2. Discovery Performance
This document describes discovery performance for certain scenarios that use RTI Security Plugins. The methodology and the tests are similar to the ones explained in the Discovery Performance section for the Core Libraries. The “No Security Libraries” values in the graphs below are equivalent to the Core Libraries (multicast) numbers, so you can compare Connext performance with and without the Security Plugins.
These numbers should only be used as a first rough approximation, since the results are highly dependent on the hardware, software configuration, and network infrastructure of the tested system. These numbers are taken with multicast enabled, since this is the default mode used by Connext for discovery.
2.4.2.1. Time to Complete Discovery
This means that all participants will create a DW and a DR for each topic.
Endpoint Discovery
The following graph displays the time it takes to complete endpoint discovery, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum times that the participants took to complete endpoint discovery. (Maximums and minimums are the dashed lines; medians are the solid lines).
The following graphs display the amount of bytes sent and received until the discovery process completes, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum bytes reported by the participants until the completion of endpoint discovery (Maximums and minimums are the dashed lines; medians are the solid lines).
As mentioned in the note above, this is a flat configuration: A single LAN with one single endpoint per participant, one participant per application and a single topic across the system. Even though this configuration can be useful for benchmarking purposes, it is not recommended for real-life applications.
In this particular multicast scenario, SPDP2’s network usage is higher than SPDP because repairs for the participant configuration packets are sent over unicast and these packets are sent from each participant to each remote participant, whereas a single SPDP multicast Participant announcement (DATA(P)) can be received via multicast by all participants.
Sent Bytes
Received Bytes
Sent Packets
Received Packets
As mentioned in the note above, this is a flat configuration: A single LAN with one single endpoint per participant, one participant per application and a single topic across the system. Even though this configuration can be useful for benchmarking purposes, it is not recommended for real-life applications.
In this particular multicast scenario, SPDP2’s network usage is higher than SPDP because repairs for the participant configuration packets are sent over unicast and these packets are sent from each participant to each remote participant, whereas a single SPDP multicast Participant announcement (DATA(P)) can be received via multicast by all participants.
Packets Sent
Packets Received
Packet Receive Errors
The following graphs display the amount of memory required by the application after completing the discovery process, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum bytes reported by the participants until the completion of endpoint discovery (Maximums and minimums are the dashed lines; medians are the solid lines).