1.1.2. Discovery Performance
This section provides the results of testing Simple Discovery in RTI Connext 7.0.0 in different scenarios, where we modify the number of participants (DomainParticipants) and endpoints (DataWriters and DataReaders).
These numbers should only be used as a first rough approximation, since the results are highly dependent on the hardware, software architecture, QoS in use, data types, and network infrastructure of the system.
1.1.2.1. Time to Complete Discovery (Unicast and Multicast)
The following test measures the time it takes to complete participant discovery as well as endpoint discovery.
To simplify the configuration, we assume the following:
Every application in the system runs a single DomainParticipant.
There is only one endpoint per DomainParticipant. Every DomainParticipant creates either a DataReader or a DataWriter.
There is only one Topic in the system.
50% of the endpoints are DataReaders, 50% are DataWriters.
We perform the tests when the entities use Unicast to discover each other and when they use Multicast.
All applications are equally distributed across all the available machines for the test.
Note
This scenario is likely not the optimal design solution for a real-life architecture. The purpose of the test is to demonstrate how powerful the Connext discovery protocol is in a flat configuration.
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.)
Sent
Received
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.)
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.)
Sent
Received
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.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: DynamicProfile_unicast, DynamicProfile
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It will also gather information about the discovery time as well as network usage and memory usage.
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch
QoS Used
1<?xml version="1.0"?>
2<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd">
4 <qos_library name="QosLibrary">
5
6 <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true">
7 <participant_factory_qos>
8 <entity_factory>
9 <autoenable_created_entities>false</autoenable_created_entities>
10 </entity_factory>
11 <!-- <logging>
12 <verbosity>WARNING</verbosity>
13 </logging> -->
14 </participant_factory_qos>
15 </qos_profile>
16
17 <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault">
18 <participant_qos>
19 <!-- This does not affect performance, but it is needed for > 1000 participants -->
20 <wire_protocol>
21 <rtps_well_known_ports>
22 <domain_id_gain>500</domain_id_gain>
23 </rtps_well_known_ports>
24 </wire_protocol>
25 <!-- To make the test a bit more fair -->
26 <transport_builtin>
27 <mask>UDPv4</mask>
28 </transport_builtin>
29 <property>
30 <value>
31 <element>
32 <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name>
33 <value>enp1s0f0</value>
34 </element>
35 <element>
36 <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name>
37 <value>1</value>
38 </element>
39 <element>
40 <name>dds.participant.property_validation_action</name>
41 <value>1</value>
42 </element>
43 </value>
44 </property>
45 </participant_qos>
46 </qos_profile>
47
48 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
49 <participant_qos>
50 <resource_limits>
51 <type_object_max_serialized_length>0</type_object_max_serialized_length>
52 <type_code_max_serialized_length>0</type_code_max_serialized_length>
53 </resource_limits>
54 <discovery_config>
55 <initial_participant_announcements>3</initial_participant_announcements>
56 <participant_liveliness_lease_duration>
57 <sec>200</sec>
58 <nanosec>0</nanosec>
59 </participant_liveliness_lease_duration>
60 <participant_liveliness_assert_period>
61 <sec>10</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_assert_period>
64 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
65 <max_liveliness_loss_detection_period>
66 <sec>10</sec>
67 <nanosec>0</nanosec>
68 </max_liveliness_loss_detection_period>
69 </discovery_config>
70 <property>
71 <value>
72 <element>
73 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
74 <value>5048576</value>
75 </element>
76 </value>
77 </property>
78 </participant_qos>
79 </qos_profile>
80
81 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
82 <participant_qos>
83 <discovery>
84 <initial_peers>
85 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
86 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
87 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
88 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
89 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
90 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
91 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
92 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
93 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
94 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
95 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
96 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
97 </initial_peers>
98 <multicast_receive_addresses></multicast_receive_addresses>
99 </discovery>
100 </participant_qos>
101 </qos_profile>
102
103 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
104 <participant_qos>
105 <discovery>
106 <initial_peers>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
117 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
118 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
119 </initial_peers>
120 <multicast_receive_addresses></multicast_receive_addresses>
121 </discovery>
122 </participant_qos>
123 </qos_profile>
124
125 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
126 <participant_qos>
127 <discovery>
128 <initial_peers>
129 <element>rtps@10.2.78.32:7400</element>
130 </initial_peers>
131 <multicast_receive_addresses></multicast_receive_addresses>
132 </discovery>
133 </participant_qos>
134 </qos_profile>
135
136 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
137 <participant_qos>
138 <discovery_config>
139 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
140 </discovery_config>
141 <property>
142 <value>
143 <element>
144 <name>dds.discovery.endpoint.lbediscovery.library</name>
145 <value>rtilbedisc</value>
146 </element>
147 <element>
148 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
149 <value>DDS_LBEDiscoveryPlugin_create</value>
150 </element>
151 <element>
152 <name>dds.discovery.endpoint.load_plugins</name>
153 <value>dds.discovery.endpoint.lbediscovery</value>
154 </element>
155 </value>
156 </property>
157 </participant_qos>
158 </qos_profile>
159
160 <!-- Security -->
161 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
162 <participant_qos>
163 <property>
164 <value>
165 <element>
166 <name>com.rti.serv.load_plugin</name>
167 <value>com.rti.serv.secure</value>
168 </element>
169 <element>
170 <name>com.rti.serv.secure.library</name>
171 <value>nddssecurity</value>
172 </element>
173 <element>
174 <name>com.rti.serv.secure.create_function</name>
175 <value>RTI_Security_PluginSuite_create</value>
176 </element>
177 <element>
178 <name>com.rti.serv.secure.authentication.ca_file</name>
179 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
180 </element>
181 <element>
182 <name>com.rti.serv.secure.authentication.private_key_file</name>
183 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
184 </element>
185 <element>
186 <name>com.rti.serv.secure.authentication.certificate_file</name>
187 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
188 </element>
189 <element>
190 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
191 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
192 </element>
193 <element>
194 <name>com.rti.serv.secure.access_control.governance_file</name>
195 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
196 </element>
197 <element>
198 <name>com.rti.serv.secure.access_control.permissions_file</name>
199 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
200 </element>
201 <element>
202 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
203 <value>auto</value>
204 </element>
205 <element>
206 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
207 <value>$(discovery_security_authentication_timeout)</value>
208 </element>
209 <element>
210 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
211 <value>$(discovery_security_authentication_request_delay)</value>
212 </element>
213 <element>
214 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
215 <value>$(discovery_security_authentication_request_timeout)</value>
216 </element>
217 </value>
218 </property>
219 </participant_qos>
220 </qos_profile>
221
222 </qos_library>
223</dds>
1.1.2.2. Limited Bandwidth Plugin (LBED)
The idea and methodology for this test are similar to the one explained above, except now we use the RTI Limited Bandwidth Plugins to see how much we can decrease bandwidth utilization and speed up the discovery process.
This test requires additional configuration files. For more information, see RTI Limited Bandwidth Plugin User’s Manual.
Note
This scenario is likely not the optimal design solution for a real-life architecture. The purpose of the test is to demonstrate how powerful the Connext discovery protocol is in a flat configuration.
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.)
Sent
Received
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.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: StaticProfile
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It also gathers information about discovery time as well as network usage and memory usage.
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch
QoS Used
1<?xml version="1.0"?>
2<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd">
4 <qos_library name="QosLibrary">
5
6 <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true">
7 <participant_factory_qos>
8 <entity_factory>
9 <autoenable_created_entities>false</autoenable_created_entities>
10 </entity_factory>
11 <!-- <logging>
12 <verbosity>WARNING</verbosity>
13 </logging> -->
14 </participant_factory_qos>
15 </qos_profile>
16
17 <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault">
18 <participant_qos>
19 <!-- This does not affect performance, but it is needed for > 1000 participants -->
20 <wire_protocol>
21 <rtps_well_known_ports>
22 <domain_id_gain>500</domain_id_gain>
23 </rtps_well_known_ports>
24 </wire_protocol>
25 <!-- To make the test a bit more fair -->
26 <transport_builtin>
27 <mask>UDPv4</mask>
28 </transport_builtin>
29 <property>
30 <value>
31 <element>
32 <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name>
33 <value>enp1s0f0</value>
34 </element>
35 <element>
36 <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name>
37 <value>1</value>
38 </element>
39 <element>
40 <name>dds.participant.property_validation_action</name>
41 <value>1</value>
42 </element>
43 </value>
44 </property>
45 </participant_qos>
46 </qos_profile>
47
48 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
49 <participant_qos>
50 <resource_limits>
51 <type_object_max_serialized_length>0</type_object_max_serialized_length>
52 <type_code_max_serialized_length>0</type_code_max_serialized_length>
53 </resource_limits>
54 <discovery_config>
55 <initial_participant_announcements>3</initial_participant_announcements>
56 <participant_liveliness_lease_duration>
57 <sec>200</sec>
58 <nanosec>0</nanosec>
59 </participant_liveliness_lease_duration>
60 <participant_liveliness_assert_period>
61 <sec>10</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_assert_period>
64 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
65 <max_liveliness_loss_detection_period>
66 <sec>10</sec>
67 <nanosec>0</nanosec>
68 </max_liveliness_loss_detection_period>
69 </discovery_config>
70 <property>
71 <value>
72 <element>
73 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
74 <value>5048576</value>
75 </element>
76 </value>
77 </property>
78 </participant_qos>
79 </qos_profile>
80
81 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
82 <participant_qos>
83 <discovery>
84 <initial_peers>
85 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
86 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
87 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
88 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
89 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
90 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
91 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
92 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
93 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
94 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
95 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
96 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
97 </initial_peers>
98 <multicast_receive_addresses></multicast_receive_addresses>
99 </discovery>
100 </participant_qos>
101 </qos_profile>
102
103 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
104 <participant_qos>
105 <discovery>
106 <initial_peers>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
117 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
118 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
119 </initial_peers>
120 <multicast_receive_addresses></multicast_receive_addresses>
121 </discovery>
122 </participant_qos>
123 </qos_profile>
124
125 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
126 <participant_qos>
127 <discovery>
128 <initial_peers>
129 <element>rtps@10.2.78.32:7400</element>
130 </initial_peers>
131 <multicast_receive_addresses></multicast_receive_addresses>
132 </discovery>
133 </participant_qos>
134 </qos_profile>
135
136 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
137 <participant_qos>
138 <discovery_config>
139 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
140 </discovery_config>
141 <property>
142 <value>
143 <element>
144 <name>dds.discovery.endpoint.lbediscovery.library</name>
145 <value>rtilbedisc</value>
146 </element>
147 <element>
148 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
149 <value>DDS_LBEDiscoveryPlugin_create</value>
150 </element>
151 <element>
152 <name>dds.discovery.endpoint.load_plugins</name>
153 <value>dds.discovery.endpoint.lbediscovery</value>
154 </element>
155 </value>
156 </property>
157 </participant_qos>
158 </qos_profile>
159
160 <!-- Security -->
161 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
162 <participant_qos>
163 <property>
164 <value>
165 <element>
166 <name>com.rti.serv.load_plugin</name>
167 <value>com.rti.serv.secure</value>
168 </element>
169 <element>
170 <name>com.rti.serv.secure.library</name>
171 <value>nddssecurity</value>
172 </element>
173 <element>
174 <name>com.rti.serv.secure.create_function</name>
175 <value>RTI_Security_PluginSuite_create</value>
176 </element>
177 <element>
178 <name>com.rti.serv.secure.authentication.ca_file</name>
179 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
180 </element>
181 <element>
182 <name>com.rti.serv.secure.authentication.private_key_file</name>
183 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
184 </element>
185 <element>
186 <name>com.rti.serv.secure.authentication.certificate_file</name>
187 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
188 </element>
189 <element>
190 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
191 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
192 </element>
193 <element>
194 <name>com.rti.serv.secure.access_control.governance_file</name>
195 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
196 </element>
197 <element>
198 <name>com.rti.serv.secure.access_control.permissions_file</name>
199 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
200 </element>
201 <element>
202 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
203 <value>auto</value>
204 </element>
205 <element>
206 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
207 <value>$(discovery_security_authentication_timeout)</value>
208 </element>
209 <element>
210 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
211 <value>$(discovery_security_authentication_request_delay)</value>
212 </element>
213 <element>
214 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
215 <value>$(discovery_security_authentication_request_timeout)</value>
216 </element>
217 </value>
218 </property>
219 </participant_qos>
220 </qos_profile>
221
222 </qos_library>
223</dds>
1.1.2.3. Participant Partitions
In this scenario, we test a new feature introduced in RTI Connext 7.0.0: DomainParticipant partitions. For more information, see PARTITION QosPolicy, in the RTI Connext Core Libraries User’s Manual.
Note
This scenario is likely not the optimal design solution for a real-life architecture. The purpose of the test is to demonstrate how powerful the Connext discovery protocol is in a flat configuration.
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.)
Sent
Received
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.)
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.)
Sent
Received
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.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: DynamicProfile_unicast, DynamicProfile
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It also gathers information about discovery time as well as network usage and memory usage.
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch
QoS Used
1<?xml version="1.0"?>
2<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd">
4 <qos_library name="QosLibrary">
5
6 <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true">
7 <participant_factory_qos>
8 <entity_factory>
9 <autoenable_created_entities>false</autoenable_created_entities>
10 </entity_factory>
11 <!-- <logging>
12 <verbosity>WARNING</verbosity>
13 </logging> -->
14 </participant_factory_qos>
15 </qos_profile>
16
17 <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault">
18 <participant_qos>
19 <!-- This does not affect performance, but it is needed for > 1000 participants -->
20 <wire_protocol>
21 <rtps_well_known_ports>
22 <domain_id_gain>500</domain_id_gain>
23 </rtps_well_known_ports>
24 </wire_protocol>
25 <!-- To make the test a bit more fair -->
26 <transport_builtin>
27 <mask>UDPv4</mask>
28 </transport_builtin>
29 <property>
30 <value>
31 <element>
32 <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name>
33 <value>enp1s0f0</value>
34 </element>
35 <element>
36 <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name>
37 <value>1</value>
38 </element>
39 <element>
40 <name>dds.participant.property_validation_action</name>
41 <value>1</value>
42 </element>
43 </value>
44 </property>
45 </participant_qos>
46 </qos_profile>
47
48 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
49 <participant_qos>
50 <resource_limits>
51 <type_object_max_serialized_length>0</type_object_max_serialized_length>
52 <type_code_max_serialized_length>0</type_code_max_serialized_length>
53 </resource_limits>
54 <discovery_config>
55 <initial_participant_announcements>3</initial_participant_announcements>
56 <participant_liveliness_lease_duration>
57 <sec>200</sec>
58 <nanosec>0</nanosec>
59 </participant_liveliness_lease_duration>
60 <participant_liveliness_assert_period>
61 <sec>10</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_assert_period>
64 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
65 <max_liveliness_loss_detection_period>
66 <sec>10</sec>
67 <nanosec>0</nanosec>
68 </max_liveliness_loss_detection_period>
69 </discovery_config>
70 <property>
71 <value>
72 <element>
73 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
74 <value>5048576</value>
75 </element>
76 </value>
77 </property>
78 </participant_qos>
79 </qos_profile>
80
81 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
82 <participant_qos>
83 <discovery>
84 <initial_peers>
85 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
86 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
87 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
88 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
89 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
90 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
91 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
92 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
93 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
94 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
95 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
96 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
97 </initial_peers>
98 <multicast_receive_addresses></multicast_receive_addresses>
99 </discovery>
100 </participant_qos>
101 </qos_profile>
102
103 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
104 <participant_qos>
105 <discovery>
106 <initial_peers>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
117 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
118 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
119 </initial_peers>
120 <multicast_receive_addresses></multicast_receive_addresses>
121 </discovery>
122 </participant_qos>
123 </qos_profile>
124
125 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
126 <participant_qos>
127 <discovery>
128 <initial_peers>
129 <element>rtps@10.2.78.32:7400</element>
130 </initial_peers>
131 <multicast_receive_addresses></multicast_receive_addresses>
132 </discovery>
133 </participant_qos>
134 </qos_profile>
135
136 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
137 <participant_qos>
138 <discovery_config>
139 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
140 </discovery_config>
141 <property>
142 <value>
143 <element>
144 <name>dds.discovery.endpoint.lbediscovery.library</name>
145 <value>rtilbedisc</value>
146 </element>
147 <element>
148 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
149 <value>DDS_LBEDiscoveryPlugin_create</value>
150 </element>
151 <element>
152 <name>dds.discovery.endpoint.load_plugins</name>
153 <value>dds.discovery.endpoint.lbediscovery</value>
154 </element>
155 </value>
156 </property>
157 </participant_qos>
158 </qos_profile>
159
160 <!-- Security -->
161 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
162 <participant_qos>
163 <property>
164 <value>
165 <element>
166 <name>com.rti.serv.load_plugin</name>
167 <value>com.rti.serv.secure</value>
168 </element>
169 <element>
170 <name>com.rti.serv.secure.library</name>
171 <value>nddssecurity</value>
172 </element>
173 <element>
174 <name>com.rti.serv.secure.create_function</name>
175 <value>RTI_Security_PluginSuite_create</value>
176 </element>
177 <element>
178 <name>com.rti.serv.secure.authentication.ca_file</name>
179 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
180 </element>
181 <element>
182 <name>com.rti.serv.secure.authentication.private_key_file</name>
183 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
184 </element>
185 <element>
186 <name>com.rti.serv.secure.authentication.certificate_file</name>
187 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
188 </element>
189 <element>
190 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
191 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
192 </element>
193 <element>
194 <name>com.rti.serv.secure.access_control.governance_file</name>
195 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
196 </element>
197 <element>
198 <name>com.rti.serv.secure.access_control.permissions_file</name>
199 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
200 </element>
201 <element>
202 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
203 <value>auto</value>
204 </element>
205 <element>
206 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
207 <value>$(discovery_security_authentication_timeout)</value>
208 </element>
209 <element>
210 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
211 <value>$(discovery_security_authentication_request_delay)</value>
212 </element>
213 <element>
214 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
215 <value>$(discovery_security_authentication_request_timeout)</value>
216 </element>
217 </value>
218 </property>
219 </participant_qos>
220 </qos_profile>
221
222 </qos_library>
223</dds>
1.1.2.4. Limiting Interfaces
The idea and methodology for this test are similar to the one explained above. In this case we aim to expore how the network usage (throughput in and out) and the discovery time changes when we announce the participants over more than one interface versus when we limit that announcement to a single interface.
Note
This scenario is likely not the optimal design solution for a real-life architecture. The purpose of the test is to demonstrate how powerful the Connext discovery protocol is in a flat configuration.
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.)
Sent
Received
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.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: StaticProfile
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It also gathers information about discovery time as well as network usage and memory usage.
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch
QoS Used
1<?xml version="1.0"?>
2<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd">
4 <qos_library name="QosLibrary">
5
6 <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true">
7 <participant_factory_qos>
8 <entity_factory>
9 <autoenable_created_entities>false</autoenable_created_entities>
10 </entity_factory>
11 <!-- <logging>
12 <verbosity>WARNING</verbosity>
13 </logging> -->
14 </participant_factory_qos>
15 </qos_profile>
16
17 <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault">
18 <participant_qos>
19 <!-- This does not affect performance, but it is needed for > 1000 participants -->
20 <wire_protocol>
21 <rtps_well_known_ports>
22 <domain_id_gain>500</domain_id_gain>
23 </rtps_well_known_ports>
24 </wire_protocol>
25 <!-- To make the test a bit more fair -->
26 <transport_builtin>
27 <mask>UDPv4</mask>
28 </transport_builtin>
29 <property>
30 <value>
31 <element>
32 <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name>
33 <value>enp1s0f0</value>
34 </element>
35 <element>
36 <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name>
37 <value>1</value>
38 </element>
39 <element>
40 <name>dds.participant.property_validation_action</name>
41 <value>1</value>
42 </element>
43 </value>
44 </property>
45 </participant_qos>
46 </qos_profile>
47
48 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
49 <participant_qos>
50 <resource_limits>
51 <type_object_max_serialized_length>0</type_object_max_serialized_length>
52 <type_code_max_serialized_length>0</type_code_max_serialized_length>
53 </resource_limits>
54 <discovery_config>
55 <initial_participant_announcements>3</initial_participant_announcements>
56 <participant_liveliness_lease_duration>
57 <sec>200</sec>
58 <nanosec>0</nanosec>
59 </participant_liveliness_lease_duration>
60 <participant_liveliness_assert_period>
61 <sec>10</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_assert_period>
64 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
65 <max_liveliness_loss_detection_period>
66 <sec>10</sec>
67 <nanosec>0</nanosec>
68 </max_liveliness_loss_detection_period>
69 </discovery_config>
70 <property>
71 <value>
72 <element>
73 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
74 <value>5048576</value>
75 </element>
76 </value>
77 </property>
78 </participant_qos>
79 </qos_profile>
80
81 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
82 <participant_qos>
83 <discovery>
84 <initial_peers>
85 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
86 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
87 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
88 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
89 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
90 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
91 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
92 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
93 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
94 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
95 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
96 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
97 </initial_peers>
98 <multicast_receive_addresses></multicast_receive_addresses>
99 </discovery>
100 </participant_qos>
101 </qos_profile>
102
103 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
104 <participant_qos>
105 <discovery>
106 <initial_peers>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
117 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
118 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
119 </initial_peers>
120 <multicast_receive_addresses></multicast_receive_addresses>
121 </discovery>
122 </participant_qos>
123 </qos_profile>
124
125 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
126 <participant_qos>
127 <discovery>
128 <initial_peers>
129 <element>rtps@10.2.78.32:7400</element>
130 </initial_peers>
131 <multicast_receive_addresses></multicast_receive_addresses>
132 </discovery>
133 </participant_qos>
134 </qos_profile>
135
136 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
137 <participant_qos>
138 <discovery_config>
139 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
140 </discovery_config>
141 <property>
142 <value>
143 <element>
144 <name>dds.discovery.endpoint.lbediscovery.library</name>
145 <value>rtilbedisc</value>
146 </element>
147 <element>
148 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
149 <value>DDS_LBEDiscoveryPlugin_create</value>
150 </element>
151 <element>
152 <name>dds.discovery.endpoint.load_plugins</name>
153 <value>dds.discovery.endpoint.lbediscovery</value>
154 </element>
155 </value>
156 </property>
157 </participant_qos>
158 </qos_profile>
159
160 <!-- Security -->
161 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
162 <participant_qos>
163 <property>
164 <value>
165 <element>
166 <name>com.rti.serv.load_plugin</name>
167 <value>com.rti.serv.secure</value>
168 </element>
169 <element>
170 <name>com.rti.serv.secure.library</name>
171 <value>nddssecurity</value>
172 </element>
173 <element>
174 <name>com.rti.serv.secure.create_function</name>
175 <value>RTI_Security_PluginSuite_create</value>
176 </element>
177 <element>
178 <name>com.rti.serv.secure.authentication.ca_file</name>
179 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
180 </element>
181 <element>
182 <name>com.rti.serv.secure.authentication.private_key_file</name>
183 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
184 </element>
185 <element>
186 <name>com.rti.serv.secure.authentication.certificate_file</name>
187 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
188 </element>
189 <element>
190 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
191 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
192 </element>
193 <element>
194 <name>com.rti.serv.secure.access_control.governance_file</name>
195 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
196 </element>
197 <element>
198 <name>com.rti.serv.secure.access_control.permissions_file</name>
199 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
200 </element>
201 <element>
202 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
203 <value>auto</value>
204 </element>
205 <element>
206 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
207 <value>$(discovery_security_authentication_timeout)</value>
208 </element>
209 <element>
210 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
211 <value>$(discovery_security_authentication_request_delay)</value>
212 </element>
213 <element>
214 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
215 <value>$(discovery_security_authentication_request_timeout)</value>
216 </element>
217 </value>
218 </property>
219 </participant_qos>
220 </qos_profile>
221
222 </qos_library>
223</dds>
1.1.2.5. SPDP2
Note
SPDP2 is an experimental feature in RTI Connext 7.0.0.
The Simple Participant Discovery Protocol 2.0 (SPDP2) is an alternative participant discovery to the Simple Participant Discovery Protocol (SPDP). SPDP2 is meant to improve scalability by reducing the amount of redundant information that is sent during participant discovery and to maintain participant liveliness.
The following graph displays the time it takes to complete endpoint discovery and participant 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.)
Endpoint Discovery Time
Participant Discovery Time
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.)
Sent
Received
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.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: DynamicProfile_unicast, DynamicProfile
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It will also gather information about the discovery time as well as network usage and memory usage.
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch
QoS Used
1<?xml version="1.0"?>
2<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd">
4 <qos_library name="QosLibrary">
5
6 <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true">
7 <participant_factory_qos>
8 <entity_factory>
9 <autoenable_created_entities>false</autoenable_created_entities>
10 </entity_factory>
11 <!-- <logging>
12 <verbosity>WARNING</verbosity>
13 </logging> -->
14 </participant_factory_qos>
15 </qos_profile>
16
17 <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault">
18 <participant_qos>
19 <!-- This does not affect performance, but it is needed for > 1000 participants -->
20 <wire_protocol>
21 <rtps_well_known_ports>
22 <domain_id_gain>500</domain_id_gain>
23 </rtps_well_known_ports>
24 </wire_protocol>
25 <!-- To make the test a bit more fair -->
26 <transport_builtin>
27 <mask>UDPv4</mask>
28 </transport_builtin>
29 <property>
30 <value>
31 <element>
32 <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name>
33 <value>enp1s0f0</value>
34 </element>
35 <element>
36 <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name>
37 <value>1</value>
38 </element>
39 <element>
40 <name>dds.participant.property_validation_action</name>
41 <value>1</value>
42 </element>
43 </value>
44 </property>
45 </participant_qos>
46 </qos_profile>
47
48 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
49 <participant_qos>
50 <resource_limits>
51 <type_object_max_serialized_length>0</type_object_max_serialized_length>
52 <type_code_max_serialized_length>0</type_code_max_serialized_length>
53 </resource_limits>
54 <discovery_config>
55 <initial_participant_announcements>3</initial_participant_announcements>
56 <participant_liveliness_lease_duration>
57 <sec>200</sec>
58 <nanosec>0</nanosec>
59 </participant_liveliness_lease_duration>
60 <participant_liveliness_assert_period>
61 <sec>10</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_assert_period>
64 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
65 <max_liveliness_loss_detection_period>
66 <sec>10</sec>
67 <nanosec>0</nanosec>
68 </max_liveliness_loss_detection_period>
69 </discovery_config>
70 <property>
71 <value>
72 <element>
73 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
74 <value>5048576</value>
75 </element>
76 </value>
77 </property>
78 </participant_qos>
79 </qos_profile>
80
81 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
82 <participant_qos>
83 <discovery>
84 <initial_peers>
85 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
86 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
87 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
88 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
89 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
90 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
91 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
92 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
93 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
94 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
95 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
96 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
97 </initial_peers>
98 <multicast_receive_addresses></multicast_receive_addresses>
99 </discovery>
100 </participant_qos>
101 </qos_profile>
102
103 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
104 <participant_qos>
105 <discovery>
106 <initial_peers>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
117 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
118 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
119 </initial_peers>
120 <multicast_receive_addresses></multicast_receive_addresses>
121 </discovery>
122 </participant_qos>
123 </qos_profile>
124
125 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
126 <participant_qos>
127 <discovery>
128 <initial_peers>
129 <element>rtps@10.2.78.32:7400</element>
130 </initial_peers>
131 <multicast_receive_addresses></multicast_receive_addresses>
132 </discovery>
133 </participant_qos>
134 </qos_profile>
135
136 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
137 <participant_qos>
138 <discovery_config>
139 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
140 </discovery_config>
141 <property>
142 <value>
143 <element>
144 <name>dds.discovery.endpoint.lbediscovery.library</name>
145 <value>rtilbedisc</value>
146 </element>
147 <element>
148 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
149 <value>DDS_LBEDiscoveryPlugin_create</value>
150 </element>
151 <element>
152 <name>dds.discovery.endpoint.load_plugins</name>
153 <value>dds.discovery.endpoint.lbediscovery</value>
154 </element>
155 </value>
156 </property>
157 </participant_qos>
158 </qos_profile>
159
160 <!-- Security -->
161 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
162 <participant_qos>
163 <property>
164 <value>
165 <element>
166 <name>com.rti.serv.load_plugin</name>
167 <value>com.rti.serv.secure</value>
168 </element>
169 <element>
170 <name>com.rti.serv.secure.library</name>
171 <value>nddssecurity</value>
172 </element>
173 <element>
174 <name>com.rti.serv.secure.create_function</name>
175 <value>RTI_Security_PluginSuite_create</value>
176 </element>
177 <element>
178 <name>com.rti.serv.secure.authentication.ca_file</name>
179 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
180 </element>
181 <element>
182 <name>com.rti.serv.secure.authentication.private_key_file</name>
183 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
184 </element>
185 <element>
186 <name>com.rti.serv.secure.authentication.certificate_file</name>
187 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
188 </element>
189 <element>
190 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
191 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
192 </element>
193 <element>
194 <name>com.rti.serv.secure.access_control.governance_file</name>
195 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
196 </element>
197 <element>
198 <name>com.rti.serv.secure.access_control.permissions_file</name>
199 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
200 </element>
201 <element>
202 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
203 <value>auto</value>
204 </element>
205 <element>
206 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
207 <value>$(discovery_security_authentication_timeout)</value>
208 </element>
209 <element>
210 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
211 <value>$(discovery_security_authentication_request_delay)</value>
212 </element>
213 <element>
214 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
215 <value>$(discovery_security_authentication_request_timeout)</value>
216 </element>
217 </value>
218 </property>
219 </participant_qos>
220 </qos_profile>
221
222 </qos_library>
223</dds>