unbounded type java

2 posts / 0 new
Last post
Offline
Last seen: 3 months 2 weeks ago
Joined: 04/02/2020
Posts: 4
unbounded type java

Hi, Im trying to add unbounded type to my project, and im not sure about the meaning of the qos required, as i feel some qos contradict the others

  1. reader_resource_limits.dynamically_allocate_fragmented_samples

  2. dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size

  3. dds.data_reader.history.memory_manager.fast_pool.pool_buffer_max_size

  4. dds.data_writer.history.memory_manager.java_stream.min_size

  5. dds.data_writer.history.memory_manager.java_stream.trim_to_size

  6. dds.data_reader.history.memory_manager.java_stream.min_size

  7. dds.data_reader.history.memory_manager.java_stream.trim_to_size

Id appreciate if anyone could explain the flow of a message and how these qos effect it?

 

irwin's picture
Offline
Last seen: 3 weeks 3 hours ago
Joined: 08/14/2010
Posts: 42

1 - reader_resource_limits.dynamically_allocate_fragmented_samples
   RTI_ConnextDDS_CoreLibraries_UsersManual.pdf Table 7.20 Field dynamically_allocate_fragmented samples

2- dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size
   RTI_ConnextDDS_CoreLibraries_UsersManual.pdf Table 21.1 DDS Sample-Data Memory Management Properties for DataWriters

3- dds.data_reader.history.memory_manager.fast_pool.pool_buffer_max_size
   RTI_ConnextDDS_CoreLibraries_UsersManual.pdf Table 21.6 Instance-Data Memory Management Properties for DataReaders

4,5 - dds.data_writer.history.memory_manager.java_stream.min_size
      dds.data_writer.history.memory_manager.java_stream.trim_to_size
   RTI_ConnextDDS_CoreLibraries_UsersManual.pdf Table 21.1 DDS Sample-Data Memory Management Properties for DataWriters Page 855

6,7- dds.data_reader.history.memory_manager.java_stream.min_size
     dds.data_reader.history.memory_manager.java_stream.trim_to_size
     RTI_ConnextDDS_CoreLibraries_UsersManual.pdf Table 21.2 DDS Sample-Data Memory Management Properties for DataReaders when
Using Java API

    Id appreciate if anyone could explain the flow of a message and how these qos effect it?
REPLY: I will give a brief overview. Normally all samples have a preallocated bugger that is defined upon code generation and
represents the maximum size that a sample can have. Without unbounded support, tha max sample size can be excessive and prohibitive.
So unbounded support allows one to tailor the average size and also allow for any message size. That is accomplished by
dynamically allocating the message buffer upon wrire and also upon sample reception.

 

                             Irwin