Solutions

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 ...
3394 reads — 0 comments
Note: Applies to NDDS 3.0 and VxWorks 5.4. Introduction The VxWorks TCP/IP stack uses a fixed amount of buffers. The buffers and their sizes are configured in the kernel. This is different from non real-time OSs, where the buffers can be taken as needed from main memory. In many NDDS applications ...
24237 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1, 4.2; While the design pattern also works for RTI Data Distribution Service 4.3 and above, its batching feature is a better way to achieve aggregation. Purpose Publisher This example shows how to create an application that aggregates data. This ...
4663 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.3x and above, Both rtiddsping and rtiddsspy can be configured to use multicast for discovery announcements by specifying a multicast address as part of the initial peer list (using -preer <PEER> ). However, rtiddsping and rtiddsspy do not have ...
5979 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.3 and above. The following example is written in C++. Publisher This throughput test is based on the throughput test in $NDDSHOME/example/CPP/performance/throughput, with modifications to batch data samples for aggregation. Instead of sending ...
3802 reads — 0 comments
If you are running RTI Analyzer on Linux and you see the following message: JVM terminated. Exit code=127 and the following error on the command shell: /usr/local/rti/RTI_Developer_Platform_1.3.0/jre/bin/java: symbol lookup error: /usr/local/rti/RTI_Developer_Platform_1.3.0/apps/RTI_Analyzer_1.3.0/ ...
3901 reads — 0 comments
Note: Applies to RTI Connext 4.x and above The message RTINetioSender_addDestination:no transport for request is a warning that RTI Connext could not find a transport for a specified peer locator. The UDPv4 and shared memory transports are installed by default. When a node tries to add a ...
4394 reads — 0 comments

Pages