performance

Due to the way in which RTI Connector handles data internally, some applications may suffer slower performance when using types that contain sequences. This is a known issue and is tracked internally in CON-42 . More specifically, this issue is seen when setting or getting a type that contains a ...
204 reads — 0 comments
If you are using Reliable communication, you could see a performance degradation due to packet loss and resending data sample fragments. This is more probable when using data bigger than 1500 Bytes (over Ethernet). In general, a DDS application using a transport such as UDPv4 splits data samples ...
2874 reads — 0 comments
Description The discovery phase in DDS applications can be considered a high throughput scenario under some circumstances. Some examples are: The applications have a lot of DDS entities. More than 2 hosts are involved. The type definitions are sent within the discovery packets (i.e., TypeCode and ...
5128 reads — 1 comment
Interrupt coalescing refers to the ability of the NIC to not interrupt the CPU immediately whenever a packet is received, but rather wait a little bit in the hope that more packets arrive. That way a single interrupt can be used to process multiple packets. This decision represent a tradeoff ...
51381 reads — 0 comments
For complex systems with hundreds of participants and endpoints, discovery may cause long startup times and high network utilization. There are several options that help increase discovery performance: 1) Reduce the size of discovery packets 1.1. You can configure the middleware to not send the ...
5247 reads — 0 comments
Performance is a function of how well hardware and software components work together with the middleware. The relationship is certainly not easily predictable. With very fast hardware, the limitation seems to be the hardware bus speed. The PCI just cannot keep up and this leads to high CPU ...
2098 reads — 0 comments
SENS/TORNADO 2.0 NETWORK STACK CONFIGURATION/PERFORMANCE ISSUES -------------------------------- 1. INTRODUCTION 1.1 NETWORK STACK VERSIONS 1.2 NET POOLS 1.2.1 CLUSTERS 1.2.2 CLUSTER BLOCKS 1.2.3 MBLOCKS 1.3 RECEIVING: DATA FLOW FROM DRIVER TO APPLICATION LEVEL 1.4 SENDING: DATA FLOW FROM ...
7514 reads — 0 comments
Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
3629 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. By default, every time you create a DDS participant with SHMEM transport enabled, the middleware creates two shared memory segments: one to receive discovery traffic and one to receive user traffic. Each one of the shared memory segments will contain a ...
4580 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. RTI Connext calls fopen() to load the default XML and NDDS_DISCOVERY_PEERS files if they exist. On some VxWorks targets that either have no file system or use NFS, FTP, or some other network-based file system, and the file system is not mounted, RTI ...
3017 reads — 0 comments

Pages

Subscribe to RSS - performance