1.2.3. Java API¶
The following tests have been performed by executing an RTI Perftest Java Publisher and Subscriber between two nodes, connected to a switch via Ethernet. The communication has been restricted to a single interface and the transport has been set to UDPv4.
Find information about the hardware, network, and command-line parameters after each of the tests.
1.2.3.1. Unkeyed, UDPv4 10Gbps Network, Java¶
The graph below shows the one-way latency without load between a Publisher and a Subscriber running in two Linux nodes in a 10Gbps network. The numbers are for best-effort as well as strict reliable reliability scenarios.
Note
We use the median (50th percentile) instead of the average in order to get a more stable measurement that does not account for spurious outliers. We also calculate the average value and other percentile values, which can be seen in the Detailed Statistics section below.
Detailed Statistics
The following tables contain the raw numbers presented by RTI Perftest. These numbers are the exact output with no further processing.
Best Effort
Sample Size (Bytes) |
Avg (μs) |
Std (μs) |
Min (μs) |
Max (μs) |
50% (μs) |
90% (μs) |
99% (μs) |
99.99% (μs) |
99.9999% (μs) |
---|---|---|---|---|---|---|---|---|---|
32 |
27 |
11.0 |
26 |
6418 |
26 |
27 |
33 |
26 |
26 |
64 |
26 |
10.6 |
25 |
6344 |
26 |
27 |
33 |
25 |
25 |
128 |
27 |
10.8 |
26 |
6385 |
26 |
28 |
34 |
26 |
26 |
256 |
28 |
10.9 |
27 |
6247 |
27 |
28 |
35 |
27 |
27 |
512 |
28 |
11.0 |
27 |
6368 |
27 |
29 |
35 |
27 |
27 |
1024 |
30 |
11.2 |
29 |
6411 |
30 |
30 |
37 |
29 |
29 |
8192 |
51 |
14.1 |
49 |
6235 |
49 |
51 |
58 |
49 |
49 |
63000 |
117 |
20.7 |
115 |
6453 |
115 |
118 |
126 |
115 |
115 |
Reliable
Sample Size (Bytes) |
Avg (μs) |
Std (μs) |
Min (μs) |
Max (μs) |
50% (μs) |
90% (μs) |
99% (μs) |
99.99% (μs) |
99.9999% (μs) |
---|---|---|---|---|---|---|---|---|---|
32 |
27 |
19.4 |
26 |
13062 |
27 |
28 |
35 |
26 |
26 |
64 |
29 |
11.2 |
28 |
6230 |
28 |
30 |
37 |
28 |
28 |
128 |
29 |
11.1 |
27 |
6297 |
27 |
30 |
37 |
27 |
27 |
256 |
30 |
11.4 |
28 |
6217 |
28 |
31 |
41 |
28 |
28 |
512 |
31 |
11.7 |
29 |
6366 |
28 |
32 |
42 |
29 |
29 |
1024 |
32 |
11.5 |
30 |
6226 |
30 |
32 |
42 |
30 |
30 |
8192 |
52 |
14.8 |
50 |
6370 |
50 |
53 |
59 |
50 |
50 |
63000 |
121 |
21.2 |
117 |
6416 |
117 |
126 |
133 |
117 |
117 |
100000 |
175 |
23.7 |
160 |
6530 |
160 |
187 |
195 |
160 |
160 |
500000 |
656 |
59.1 |
547 |
7191 |
624 |
698 |
727 |
547 |
547 |
1048576 |
1289 |
94.7 |
1110 |
7687 |
1270 |
1403 |
1494 |
1110 |
1110 |
1548576 |
2012 |
162.5 |
1678 |
8477 |
1934 |
2188 |
2304 |
1678 |
1678 |
4194304 |
6044 |
2124.3 |
5411 |
40574 |
5549 |
5934 |
10539 |
5411 |
5411 |
10485760 |
15889 |
5608.0 |
14490 |
50095 |
14802 |
15397 |
49792 |
14490 |
14490 |
Perftest Scripts
To produce these tests, we executed RTI Perftest for C++98. The exact commands used can be found here:
Publisher Side
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | sudo /set_lat_mode.sh
echo EXECUTABLE IS $1
export executable=$1
echo OUTPUT PATH IS $2
export output_folder=$2
export exec_time=30
export nic=172.16.0.1
export pub_string="-pub \
-transport UDPv4 \
-nic $nic \
-noPrint \
-noOutputHeaders \
-exec $exec_time \
-latencyTest"
mkdir -p $output_folder
echo ">> UNKEYED BE"
export my_file=$output_folder/lat_udpv4_pub_unkeyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best -datalen $DATALEN $pub_string"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> UNKEYED REL"
export my_file=$output_folder/lat_udpv4_pub_unkeyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000 100000 500000 1048576 1548576 4194304 10485760; do
export command="taskset -c 0 \
$executable -datalen $DATALEN $pub_string"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> KEYED BE"
export my_file=$output_folder/lat_udpv4_pub_keyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best -keyed -instances 100000 -datalen $DATALEN $pub_string"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> KEYED REL"
export my_file=$output_folder/lat_udpv4_pub_keyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -keyed -instances 100000 -datalen $DATALEN $pub_string"
echo $command
$command >> $my_file;
sleep 3;
done
|
Subscriber Side
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 | sudo /set_lat_mode.sh
echo EXECUTABLE IS $1
export executable=$1
echo OUTPUT PATH IS $2
export output_folder=$2
export nic=172.16.0.2
export sub_string="-sub \
-transport UDPv4 \
-nic $nic \
-noPrint \
-noOutputHeaders"
mkdir -p $output_folder
echo ">> UNKEYED BE"
export my_file=$output_folder/lat_udpv4_sub_unkeyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> UNKEYED REL"
export my_file=$output_folder/lat_udpv4_sub_unkeyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000 100000 500000 1048576 1548576 4194304 10485760; do
export command="taskset -c 0 \
$executable $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> KEYED BE"
export my_file=$output_folder/lat_udpv4_sub_keyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best -keyed -instances 100000 $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> KEYED REL"
export my_file=$output_folder/lat_udpv4_sub_keyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -keyed -instances 100000 $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
|
Test Hardware
The following hardware was used to perform these tests:
Linux Nodes
Processor: Intel® Xeon® E-2186G 3.8GHz, 12M cache, 6C/12T, turbo (95W)
RAM: 16GB 2666MT/s DDR4 ECC UDIMM
NIC 1: Intel X550 Dual Port 10GbE BASE-T Adapter, PCIe Full Height
NIC 2: Intel Ethernet I350 Dual Port 1GbE BASE-T Adapter, PCIe Low Profile
OS: Ubuntu 18.04 -- gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Switch
Dell Networking S4048T-ON, 48x 10GBASE-T and 6x 40GbE QSFP+ ports, IO to PSU air, 2x AC PSU, OS9
The graph below shows the expected throughput behavior when performing a 1-1 communication between two Linux nodes in a 10Gbps network. The numbers are for best-effort as well as strict reliable reliability scenarios.
Note
By default, RTI Perftest enables batching when performing a Maximum Throughput test. The batching feature allows sending more than one data sample per RTPS packet, improving network performance for small data sizes. See the RTI Connext DDS Core Libraries User’s Manual for more information on batching.
The batch maximum size is set by RTI Perftest to be 8192 bytes; after 8192 bytes, batching is not enabled.
Detailed Statistics
This table contains the raw numbers presented by RTI Perftest. These numbers are the exact output with no further processing.
Best Effort
Sample Size (Bytes) |
Total Samples |
Avg Samples/s |
Avg Mbps |
Lost Samples |
Lost Samples (%) |
---|---|---|---|---|---|
32 |
26583552 |
884630 |
236.5 |
40684568 |
60.48 |
64 |
26312576 |
875316 |
448.2 |
31236923 |
54.28 |
128 |
25442193 |
846366 |
866.7 |
29844224 |
53.98 |
256 |
23704000 |
788560 |
1615.0 |
24644640 |
50.97 |
512 |
20665872 |
687493 |
2816.0 |
17975952 |
46.52 |
1024 |
16447528 |
547150 |
4482.3 |
10472776 |
38.90 |
8192 |
4488979 |
149631 |
9806.2 |
11496 |
0.26 |
63000 |
588351 |
19612 |
9884.4 |
1025 |
0.17 |
Reliable
Sample Size (Bytes) |
Total Samples |
Avg Samples/s |
Avg Mbps |
Lost Samples |
Lost Samples (%) |
---|---|---|---|---|---|
32 |
26645706 |
888056 |
227.4 |
0 |
0.00 |
64 |
26570260 |
885504 |
453.4 |
0 |
0.00 |
128 |
25050382 |
834927 |
855.0 |
0 |
0.00 |
256 |
23215259 |
773796 |
1584.7 |
0 |
0.00 |
512 |
19056176 |
634970 |
2800.8 |
0 |
0.00 |
1024 |
15542328 |
518056 |
4243.9 |
0 |
0.00 |
8192 |
4279327 |
142645 |
9348.4 |
0 |
0.00 |
63000 |
588258 |
19608 |
9882.6 |
0 |
0.00 |
100000 |
369451 |
12314 |
9850.8 |
0 |
0.00 |
500000 |
66521 |
2217 |
8869.2 |
0 |
0.00 |
1048576 |
28818 |
960 |
8055.5 |
0 |
0.00 |
1548576 |
21011 |
699 |
8661.3 |
0 |
0.00 |
4194304 |
7270 |
242 |
8133.0 |
0 |
0.00 |
10485760 |
2657 |
89 |
7427.3 |
0 |
0.00 |
Perftest Scripts
To produce these tests, we executed RTI Perftest for C++98. The exact commands used can be found here:
Publisher Side
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 | sudo /set_thr_mode.sh
echo EXECUTABLE IS $1
export executable=$1
echo OUTPUT PATH IS $2
export output_folder=$2
export exec_time=30
export nic=172.16.0.1
export pub_string="-pub \
-transport UDPv4 \
-nic $nic \
-noPrint \
-noOutputHeaders \
-exec $exec_time"
mkdir -p $output_folder
echo ">> UNKEYED BE"
export my_file=$output_folder/thr_udpv4_pub_unkeyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best $pub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> UNKEYED REL"
export my_file=$output_folder/thr_udpv4_pub_unkeyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000 100000 500000 1048576 1548576 4194304 10485760; do
export command="taskset -c 0 \
$executable $pub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> KEYED BE"
export my_file=$output_folder/thr_udpv4_pub_keyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best -keyed -instances 100000 $pub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 3;
done
sleep 5;
echo ">> KEYED REL"
export my_file=$output_folder/thr_udpv4_pub_keyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -keyed -instances 100000 $pub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 3;
done
|
Subscriber Side
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 | sudo /set_thr_mode.sh
echo EXECUTABLE IS $1
export executable=$1
echo OUTPUT PATH IS $2
export output_folder=$2
export nic=172.16.0.2
export sub_string="-sub \
-transport UDPv4 \
-nic $nic \
-noPrint \
-noOutputHeaders"
mkdir -p $output_folder
echo ">> UNKEYED BE"
export my_file=$output_folder/thr_udpv4_sub_unkeyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> UNKEYED REL"
export my_file=$output_folder/thr_udpv4_sub_unkeyed_rel.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000 100000 500000 1048576 1548576 4194304 10485760; do
export command="taskset -c 0 \
$executable $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> KEYED BE"
export my_file=$output_folder/thr_udpv4_sub_keyed_be.csv
touch $my_file
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -best -keyed -instances 100000 $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
sleep 5;
echo ">> KEYED REL"
touch $my_file
export my_file=$output_folder/thr_udpv4_sub_keyed.csv
for DATALEN in 32 64 128 256 512 1024 8192 63000; do
export command="taskset -c 0 \
$executable -keyed -instances 100000 $sub_string -datalen $DATALEN"
echo $command
$command >> $my_file;
sleep 10;
done
|
Test Hardware
The following hardware was used to perform these tests:
Linux Nodes
Processor: Intel® Xeon® E-2186G 3.8GHz, 12M cache, 6C/12T, turbo (95W)
RAM: 16GB 2666MT/s DDR4 ECC UDIMM
NIC 1: Intel X550 Dual Port 10GbE BASE-T Adapter, PCIe Full Height
NIC 2: Intel Ethernet I350 Dual Port 1GbE BASE-T Adapter, PCIe Low Profile
OS: Ubuntu 18.04 -- gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Switch
Dell Networking S4048T-ON, 48x 10GBASE-T and 6x 40GbE QSFP+ ports, IO to PSU air, 2x AC PSU, OS9
1.2.3.2. Keyed, UDPv4 10Gbps Network, Java¶
The graph below shows the one-way latency without load between a Publisher and a Subscriber running in two Linux nodes in a 10Gbps network. The numbers are for best-effort as well as strict reliable reliability scenarios.
Note
We use the median (50th percentile) instead of the average in order to get a more stable measurement that does not account for spurious outliers. We also calculate the average value and other percentile values, which can be seen in the Detailed Statistics section below.
Detailed Statistics
The following tables contain the raw numbers presented by RTI Perftest. These numbers are the exact output with no further processing.
Best Effort
Sample Size (Bytes) |
Avg (μs) |
Std (μs) |
Min (μs) |
Max (μs) |
50% (μs) |
90% (μs) |
99% (μs) |
99.99% (μs) |
99.9999% (μs) |
---|---|---|---|---|---|---|---|---|---|
32 |
26 |
18.8 |
25 |
13070 |
26 |
26 |
33 |
25 |
25 |
64 |
26 |
19.1 |
25 |
13183 |
26 |
26 |
33 |
25 |
25 |
128 |
27 |
19.2 |
25 |
13167 |
26 |
27 |
32 |
25 |
25 |
256 |
27 |
19.3 |
26 |
13210 |
27 |
27 |
33 |
26 |
26 |
512 |
28 |
19.6 |
27 |
13184 |
28 |
28 |
35 |
27 |
27 |
1024 |
29 |
20.0 |
28 |
13204 |
29 |
29 |
34 |
28 |
28 |
8192 |
50 |
25.4 |
48 |
13181 |
49 |
50 |
57 |
48 |
48 |
63000 |
117 |
38.9 |
115 |
13312 |
116 |
118 |
125 |
115 |
115 |
Reliable
Sample Size (Bytes) |
Avg (μs) |
Std (μs) |
Min (μs) |
Max (μs) |
50% (μs) |
90% (μs) |
99% (μs) |
99.99% (μs) |
99.9999% (μs) |
---|---|---|---|---|---|---|---|---|---|
32 |
32 |
23.8 |
31 |
9342 |
32 |
33 |
36 |
31 |
31 |
64 |
32 |
24.6 |
31 |
9817 |
32 |
33 |
36 |
31 |
31 |
128 |
33 |
23.9 |
31 |
9484 |
32 |
33 |
36 |
31 |
31 |
256 |
34 |
28.4 |
32 |
13076 |
33 |
34 |
37 |
32 |
32 |
512 |
34 |
27.7 |
32 |
12385 |
33 |
34 |
37 |
32 |
32 |
1024 |
36 |
24.4 |
34 |
9447 |
35 |
36 |
39 |
34 |
34 |
8192 |
56 |
34.9 |
54 |
12481 |
56 |
57 |
59 |
54 |
54 |
63000 |
125 |
54.2 |
121 |
13578 |
124 |
126 |
131 |
121 |
121 |
Perftest Scripts
To produce these tests, we executed RTI Perftest for C++98. The exact commands used can be found here:
Publisher Side
Subscriber Side
Test Hardware
The following hardware was used to perform these tests:
Linux Nodes
Processor: Intel® Xeon® E-2186G 3.8GHz, 12M cache, 6C/12T, turbo (95W)
RAM: 16GB 2666MT/s DDR4 ECC UDIMM
NIC 1: Intel X550 Dual Port 10GbE BASE-T Adapter, PCIe Full Height
NIC 2: Intel Ethernet I350 Dual Port 1GbE BASE-T Adapter, PCIe Low Profile
OS: Ubuntu 18.04 -- gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Switch
Dell Networking S4048T-ON, 48x 10GBASE-T and 6x 40GbE QSFP+ ports, IO to PSU air, 2x AC PSU, OS9
The graph below shows the expected throughput behavior when performing a 1-1 communication between two Linux nodes in a 10Gbps network. The numbers are for best-effort as well as strict reliable reliability scenarios.
Note
By default, RTI Perftest enables batching when performing a Maximum Throughput test. The batching feature allows sending more than one data sample per RTPS packet, improving network performance for small data sizes. See the RTI Connext DDS Core Libraries User’s Manual for more information on batching.
The batch maximum size is set by RTI Perftest to be 8192 bytes; after 8192 bytes, batching is not enabled.
Detailed Statistics
This table contains the raw numbers presented by RTI Perftest. These numbers are the exact output with no further processing.
Best Effort
Sample Size (Bytes) |
Total Samples |
Avg Samples/s |
Avg Mbps |
Lost Samples |
Lost Samples (%) |
---|---|---|---|---|---|
32 |
17584896 |
585109 |
149.8 |
5640702 |
24.29 |
64 |
17316992 |
576094 |
295.0 |
5371904 |
23.68 |
128 |
16947030 |
563775 |
577.3 |
4682816 |
21.65 |
256 |
15925658 |
529794 |
1085.0 |
4675424 |
22.70 |
512 |
14381888 |
478437 |
1959.7 |
3740336 |
20.64 |
1024 |
12027256 |
400095 |
3277.6 |
3181792 |
20.92 |
8192 |
3984275 |
132798 |
8703.1 |
509171 |
11.33 |
63000 |
589444 |
19648 |
9902.7 |
377 |
0.06 |
Reliable
Sample Size (Bytes) |
Total Samples |
Avg Samples/s |
Avg Mbps |
Lost Samples |
Lost Samples (%) |
---|---|---|---|---|---|
32 |
16196609 |
539620 |
138.1 |
0 |
0.00 |
64 |
16173953 |
538970 |
276.0 |
0 |
0.00 |
128 |
15659820 |
521926 |
534.5 |
0 |
0.00 |
256 |
14619321 |
487282 |
998.0 |
0 |
0.00 |
512 |
13164705 |
438814 |
1797.4 |
0 |
0.00 |
1024 |
11128342 |
370942 |
3038.8 |
0 |
0.00 |
8192 |
3529186 |
117637 |
7709.4 |
0 |
0.00 |
63000 |
587574 |
19585 |
9871.0 |
0 |
0.00 |
Perftest Scripts
To produce these tests, we executed RTI Perftest for C++98. The exact commands used can be found here:
Publisher Side
Subscriber Side
Test Hardware
The following hardware was used to perform these tests:
Linux Nodes
Processor: Intel® Xeon® E-2186G 3.8GHz, 12M cache, 6C/12T, turbo (95W)
RAM: 16GB 2666MT/s DDR4 ECC UDIMM
NIC 1: Intel X550 Dual Port 10GbE BASE-T Adapter, PCIe Full Height
NIC 2: Intel Ethernet I350 Dual Port 1GbE BASE-T Adapter, PCIe Low Profile
OS: Ubuntu 18.04 -- gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Switch
Dell Networking S4048T-ON, 48x 10GBASE-T and 6x 40GbE QSFP+ ports, IO to PSU air, 2x AC PSU, OS9