memory

In a scenario where multiple DataWriters come up and go away in the system, a matching DataReader application will experience a continual memory growth, this may be confused with a memory leak. This observed behavior is due to the fact that DataReader entities must maintain information about the ...
3140 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 ...
18237 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The first and foremost step to reducing the memory footprint is an architectural review. The number of topics, the queue sizes, whether or not you use keys, the number of domains, or the usage of partitions have a great impact on the memory footprint of ...
4398 reads — 0 comments
Note: Applies to RTI Connext versions 4.x and above Configuration data structures such as QoS structures are passed to RTI Connext by value, as they are only used to initialize the internal state of the entity being created. After the call to create the object, the user application can free the ...
1853 reads — 0 comments
Subscribe to RSS - memory