3.2.2.1. LightWeight Security PSK vs HMAC Only vs Full Security PSK
In RTI Connext 7.1 we introduced Pre-Shared Key Protection (PSK)` to secure the RTPS communication.
This PSK can be leveraged in two ways: As a part of RTI Security Plugins, protecting bootstrapping
communications before authentication is successfully concluded or as a dedicated library named RTI
Lightweight Security Plugins, where PSK` is the only option and protects the entirety of the communication.
PSK can be configured to use various cryptographic algorithms: AES128 or AES256 in GCM
(for both integrity and confidentiality) mode.
In RTI Connext 7.1 we deprecated HMAC-only mode which is scheduled to be superseded in the next release with Lightweight Security.
It supports non-configurable HMAC-SHA256 which only protects data integrity without its confidentiality.
Charts below compare performance of the Lightweight Security’s AES256 GCM algorithm
with HMAC-only and a non-secure scenario. We show here that PSK performs better than HMAC-only.
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_security
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.
The Middleware version used to perform these tests is:
RTI Connext DDS 7.1.0 Host and Target Libraries for x64 Linux (x64Linux4gcc7.3.0)
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 (10Gbps and 1Gbps interfaces)
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>$(interface_name)</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 <element>
44 <name>dds.transport.UDPv4.builtin.gather_detailed_statistics</name>
45 <value>$(gather_detailed_statistics)</value>
46 </element>
47 </value>
48 </property>
49 </participant_qos>
50 </qos_profile>
51
52 <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true">
53 <participant_qos>
54 <resource_limits>
55 <type_object_max_serialized_length>0</type_object_max_serialized_length>
56 <type_code_max_serialized_length>0</type_code_max_serialized_length>
57 </resource_limits>
58 <discovery_config>
59 <initial_participant_announcements>5</initial_participant_announcements>
60 <participant_liveliness_lease_duration>
61 <sec>200</sec>
62 <nanosec>0</nanosec>
63 </participant_liveliness_lease_duration>
64 <participant_liveliness_assert_period>
65 <sec>5</sec>
66 <nanosec>0</nanosec>
67 </participant_liveliness_assert_period>
68 <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind>
69 <max_liveliness_loss_detection_period>
70 <sec>10</sec>
71 <nanosec>0</nanosec>
72 </max_liveliness_loss_detection_period>
73 </discovery_config>
74 <property>
75 <value>
76 <element>
77 <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name>
78 <value>5048576</value>
79 </element>
80 </value>
81 </property>
82 </participant_qos>
83 </qos_profile>
84
85 <qos_profile name="DynamicProfile_DefaultQoS_SPDP2" base_name="QosLibrary::DynamicProfile_DefaultQoS">
86 <participant_qos>
87 <discovery_config>
88 <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins>
89 </discovery_config>
90 </participant_qos>
91 </qos_profile>
92
93 <qos_profile name="DynamicProfile_SPDP2" base_name="QosLibrary::DynamicProfile">
94 <participant_qos>
95 <discovery_config>
96 <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins>
97 </discovery_config>
98 </participant_qos>
99 </qos_profile>
100
101 <qos_profile name="Unicast_10Gbps_lab_snippet">
102 <participant_qos>
103 <discovery>
104 <initial_peers>
105 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element>
106 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element>
107 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element>
108 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element>
109 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element>
110 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element>
111 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element>
112 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element>
113 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element>
114 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element>
115 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element>
116 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element>
117 </initial_peers>
118 <multicast_receive_addresses></multicast_receive_addresses>
119 </discovery>
120 </participant_qos>
121 </qos_profile>
122
123 <qos_profile name="Unicast_1Gbps_lab_snippet">
124 <participant_qos>
125 <discovery>
126 <initial_peers>
127 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.20</element>
128 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.21</element>
129 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.22</element>
130 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.23</element>
131 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.24</element>
132 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.25</element>
133 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.26</element>
134 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.27</element>
135 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.28</element>
136 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.29</element>
137 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.30</element>
138 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.31</element>
139 </initial_peers>
140 <multicast_receive_addresses></multicast_receive_addresses>
141 </discovery>
142 </participant_qos>
143 </qos_profile>
144
145 <qos_profile name="Unicast_pi_lab_snippet">
146 <participant_qos>
147 <discovery>
148 <initial_peers>
149 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.41</element>
150 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.42</element>
151 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.43</element>
152 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.44</element>
153 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.45</element>
154 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.46</element>
155 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.47</element>
156 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.48</element>
157 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.49</element>
158 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.50</element>
159 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.51</element>
160 <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.52</element>
161 </initial_peers>
162 <multicast_receive_addresses></multicast_receive_addresses>
163 </discovery>
164 </participant_qos>
165 </qos_profile>
166
167 <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile">
168 <base_name>
169 <element>QosLibrary::Unicast_10Gbps_lab_snippet</element>
170 </base_name>
171 </qos_profile>
172
173 <qos_profile name="DynamicProfile_unicast_eno2" base_name="QosLibrary::DynamicProfile">
174 <base_name>
175 <element>QosLibrary::Unicast_1Gbps_lab_snippet</element>
176 </base_name>
177 </qos_profile>
178
179 <qos_profile name="DynamicProfile_unicast_eth0" base_name="QosLibrary::DynamicProfile">
180 <base_name>
181 <element>QosLibrary::Unicast_pi_lab_snippet</element>
182 </base_name>
183 </qos_profile>
184
185 <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS">
186 <base_name>
187 <element>QosLibrary::Unicast_10Gbps_lab_snippet</element>
188 </base_name>
189 </qos_profile>
190
191 <qos_profile name="DynamicProfile_unicast_SPDP2" base_name="QosLibrary::DynamicProfile_SPDP2">
192 <base_name>
193 <element>QosLibrary::Unicast_10Gbps_lab_snippet</element>
194 </base_name>
195 </qos_profile>
196
197 <qos_profile name="DynamicProfile_unicast_SPDP2_eno2" base_name="QosLibrary::DynamicProfile_SPDP2">
198 <base_name>
199 <element>QosLibrary::Unicast_1Gbps_lab_snippet</element>
200 </base_name>
201 </qos_profile>
202
203 <qos_profile name="DynamicProfile_unicast_SPDP2_eth0" base_name="QosLibrary::DynamicProfile_SPDP2">
204 <base_name>
205 <element>QosLibrary::Unicast_pi_lab_snippet</element>
206 </base_name>
207 </qos_profile>
208
209 <qos_profile name="DynamicProfile_unicast_DefaultQoS_SPDP2" base_name="QosLibrary::DynamicProfile_DefaultQoS_SPDP2">
210 <base_name>
211 <element>QosLibrary::Unicast_10Gbps_lab_snippet</element>
212 </base_name>
213 </qos_profile>
214
215 <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile">
216 <participant_qos>
217 <discovery>
218 <initial_peers>
219 <element>rtps@10.2.78.32:7400</element>
220 </initial_peers>
221 <multicast_receive_addresses></multicast_receive_addresses>
222 </discovery>
223 </participant_qos>
224 </qos_profile>
225
226 <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile">
227 <participant_qos>
228 <discovery_config>
229 <builtin_discovery_plugins>SPDP</builtin_discovery_plugins>
230 </discovery_config>
231 <property>
232 <value>
233 <element>
234 <name>dds.discovery.endpoint.lbediscovery.library</name>
235 <value>rtilbedisc</value>
236 </element>
237 <element>
238 <name>dds.discovery.endpoint.lbediscovery.create_function</name>
239 <value>DDS_LBEDiscoveryPlugin_create</value>
240 </element>
241 <element>
242 <name>dds.discovery.endpoint.load_plugins</name>
243 <value>dds.discovery.endpoint.lbediscovery</value>
244 </element>
245 </value>
246 </property>
247 </participant_qos>
248 </qos_profile>
249
250 <!-- Security -->
251 <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile">
252 <participant_qos>
253 <property>
254 <value>
255 <element>
256 <name>com.rti.serv.load_plugin</name>
257 <value>com.rti.serv.secure</value>
258 </element>
259 <element>
260 <name>com.rti.serv.secure.library</name>
261 <value>nddssecurity</value>
262 </element>
263 <element>
264 <name>com.rti.serv.secure.create_function</name>
265 <value>RTI_Security_PluginSuite_create</value>
266 </element>
267 <element>
268 <name>com.rti.serv.secure.authentication.ca_file</name>
269 <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value>
270 </element>
271 <element>
272 <name>com.rti.serv.secure.authentication.private_key_file</name>
273 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value>
274 </element>
275 <element>
276 <name>com.rti.serv.secure.authentication.certificate_file</name>
277 <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value>
278 </element>
279 <element>
280 <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
281 <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value>
282 </element>
283 <element>
284 <name>com.rti.serv.secure.access_control.governance_file</name>
285 <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value>
286 </element>
287 <element>
288 <name>com.rti.serv.secure.access_control.permissions_file</name>
289 <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value>
290 </element>
291 <element>
292 <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name>
293 <value>auto</value>
294 </element>
295 <element>
296 <name>dds.participant.trust_plugins.authentication_timeout.sec</name>
297 <value>$(discovery_security_authentication_timeout)</value>
298 </element>
299 <element>
300 <name>dds.participant.trust_plugins.authentication_request_delay.sec</name>
301 <value>$(discovery_security_authentication_request_delay)</value>
302 </element>
303 <element>
304 <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name>
305 <value>$(discovery_security_authentication_request_timeout)</value>
306 </element>
307 <element>
308 <name>com.rti.serv.secure.authentication.enable_custom_algorithms</name>
309 <value>true</value>
310 </element>
311 </value>
312 </property>
313 </participant_qos>
314 </qos_profile>
315
316 <!-- Security -->
317 <qos_profile name="DynamicProfileSecurity_SPDP2" base_name="QosLibrary::DynamicProfileSecurity">
318 <participant_qos>
319 <discovery_config>
320 <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins>
321 </discovery_config>
322 </participant_qos>
323 </qos_profile>
324
325 <!-- Security HMAC ONLY -->
326 <qos_profile name="DynamicProfileSecurity_HMAC" base_name="QosLibrary::DynamicProfile">
327 <participant_qos>
328 <property>
329 <value>
330 <element>
331 <name>com.rti.serv.load_plugin</name>
332 <value>com.rti.serv.secure</value>
333 </element>
334 <element>
335 <name>com.rti.serv.secure.library</name>
336 <value>nddssecurity</value>
337 </element>
338 <element>
339 <name>com.rti.serv.secure.create_function</name>
340 <value>RTI_Security_PluginSuite_create</value>
341 </element>
342 <element>
343 <name>com.rti.serv.secure.hmac_only.enabled</name>
344 <value>1</value>
345 </element>
346 <element>
347 <name>com.rti.serv.secure.hmac_only.cryptography.key</name>
348 <value>str:SecretKey</value>
349 </element>
350 </value>
351 </property>
352 </participant_qos>
353 </qos_profile>
354
355
356 <!-- Security + PSK-->
357 <qos_profile name="DynamicProfileSecurity_PSK" base_name="QosLibrary::DynamicProfileSecurity">
358 <participant_qos>
359 <discovery_config>
360 <default_domain_announcement_period>
361 <sec>DURATION_INFINITE_SEC</sec>
362 <nanosec>DURATION_INFINITE_NSEC</nanosec>
363 </default_domain_announcement_period>
364 </discovery_config>
365 <property>
366 <value>
367 <element>
368 <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key</name>
369 <value>SecretKey</value>
370 </element>
371 </value>
372 </property>
373 </participant_qos>
374 </qos_profile>
375
376 <!-- LW Security + PSK -->
377 <qos_profile name="DynamicProfileLWS_PSK" base_name="QosLibrary::DynamicProfile">
378 <participant_qos>
379 <discovery_config>
380 <default_domain_announcement_period>
381 <sec>DURATION_INFINITE_SEC</sec>
382 <nanosec>DURATION_INFINITE_NSEC</nanosec>
383 </default_domain_announcement_period>
384 </discovery_config>
385 <property>
386 <value>
387 <element>
388 <name>com.rti.serv.load_plugin</name>
389 <value>com.rti.serv.secure</value>
390 </element>
391 <element>
392 <name>com.rti.serv.secure.library</name>
393 <value>nddslightweightsecurity</value>
394 </element>
395 <element>
396 <name>com.rti.serv.secure.create_function</name>
397 <value>RTI_Security_PluginSuite_create</value>
398 </element>
399
400 <element>
401 <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key</name>
402 <value>SecretKey</value>
403 </element>
404 <element>
405 <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key_algorithm</name>
406 <value>$(lws_psk_algorithm)</value>
407 </element>
408 </value>
409 </property>
410 </participant_qos>
411 </qos_profile>
412
413 </qos_library>
414</dds>
3.2.2.2. openSSL 3.0 vs openSSL 1.1.1
This section compares the performance of the cryptographic libraries that RTI Connext supports. We compare the performance of the OpenSSL 3, and OpenSSL 1.1.1 cryptographic libraries. Changes in the patch versions of those libraries (last digit in the OpenSSL 3, letter in the OpenSSL 1 version number) should not have a great effect on the performance results.
Notice that these tests use the cryptographic libraries along to the RTI Connext code, however, in order to prove that these differences are not due to the RTI Connext specific code we also gathered some metrics isolating the Cryptographic operations, see Cryptographic Libraries section.
Endpoint Discovery
Sent
Received
3.2.2.3. Ephemeral Keys Pairs for the Key Agreement Algorithm (7.0.0)
Note
This change was added for 7.0.0. Issue reference is SEC-1676
Sent
Received
3.2.2.4. 7.0.0 vs 6.1.1 (Security Governance Configuration Levels)
Sent
Received
3.2.2.5. Comparison between 6.1.1 and 6.0.1
Due to several improvements added in Connext DDS and Security Plugins in 6.1.0, you will see big improvements in discovery time in 6.1.1 (and 6.1.0). The following graph and tables show the results of the tests above done for both 6.0.1 and 6.1.1.
Note
Note that the numbers used to compare these two releases were taken independently, in a different laboratory, hence the mismatch between these numbers and the ones above See the hardware information for more details.
Time to complete Discovery (Seconds)
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
2.7320 |
3.0650 |
3.1160 |
3.3220 |
75 |
3.0160 |
3.5920 |
3.6760 |
3.8000 |
100 |
3.4170 |
4.2510 |
6.4510 |
6.1540 |
125 |
4.2110 |
8.1120 |
8.2910 |
8.7180 |
150 |
5.1460 |
11.2380 |
10.3900 |
10.5340 |
175 |
6.0260 |
14.2170 |
13.2850 |
13.2770 |
200 |
6.8690 |
15.0870 |
17.2230 |
17.1860 |
225 |
8.2230 |
18.6980 |
20.9340 |
21.5640 |
250 |
9.8220 |
24.4040 |
26.5830 |
26.7730 |
275 |
12.1190 |
28.1240 |
32.0280 |
32.5500 |
300 |
13.6740 |
32.6540 |
37.4390 |
38.4670 |
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
2.630 |
3.101 |
5.071 |
5.093 |
75 |
3.446 |
3.766 |
5.706 |
7.085 |
100 |
4.011 |
4.541 |
9.122 |
9.024 |
125 |
5.165 |
10.544 |
14.980 |
15.788 |
150 |
6.148 |
11.256 |
23.689 |
25.663 |
175 |
8.081 |
14.872 |
38.195 |
39.401 |
200 |
9.589 |
18.650 |
56.997 |
59.554 |
225 |
12.328 |
21.932 |
78.655 |
80.577 |
250 |
17.073 |
27.133 |
102.576 |
106.598 |
275 |
18.369 |
35.549 |
129.574 |
135.227 |
300 |
21.289 |
39.642 |
160.880 |
165.835 |
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
0.10 |
-0.04 |
-1.95 |
-1.77 |
75 |
-0.43 |
-0.17 |
-2.03 |
-3.29 |
100 |
-0.59 |
-0.29 |
-2.67 |
-2.87 |
125 |
-0.95 |
-2.43 |
-6.69 |
-7.07 |
150 |
-1.00 |
-0.02 |
-13.30 |
-15.13 |
175 |
-2.05 |
-0.65 |
-24.91 |
-26.12 |
200 |
-2.72 |
-3.56 |
-39.77 |
-42.37 |
225 |
-4.10 |
-3.23 |
-57.72 |
-59.01 |
250 |
-7.25 |
-2.73 |
-75.99 |
-79.83 |
275 |
-6.25 |
-7.43 |
-97.55 |
-102.68 |
300 |
-7.62 |
-6.99 |
-123.44 |
-127.37 |
For more information about the improvements that account for these gains, see:
- “Improved support for concurrency in data reception events in
DataReaders in a DomainParticipant” in the Core Libraries’s Performance Improvements
- “Improved discovery scalability when using BuiltinQosLib::Generic.Security profile”
in the Security Plugins’s Changes Related to Scalability
- “Endpoint state transition improvements for key distribution”
in the Security Plugins’s Changes Related to Scalability
- “Potentially very long recovery times for timed-out authentications”
in the Security Plugins’s Fixes Related to Scalability
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 (10Gbps and 1Gbps interfaces)