.. _`DDS_DomainParticipantFactory_get_instance()`: ../../api_c/html/group__DDSDomainParticipantFactoryModule.html#gac874268715a20b82db24d26d7fbae965 .. _`DDS_WaitSet_new()`: ../../api_c/html/group__DDSConditionsModule.html#ga5490c5e53e46790c2823d43310141c7b .. _`DDS_DomainParticipantFactory_create_participant()`: ../../api_c/html/group__DDSDomainParticipantFactoryModule.html#ga325cf8f97a2752b6f486b7b1c3faf5b8 .. _`DDS_DomainParticipantFactory_finalize_instance()`: ../../api_c/html/group__DDSDomainParticipantFactoryModule.html#ga925b60f4abd015d1ecd3a389feebfa6c .. _`OSAPI_Waitset_delete()`: ../../api_c/html/group__DDSConditionsModule.html#ga06bf93bc3887f0f5b92ddcfa4f5bfa18 .. _`DDS_String_free()`: ../../api_c/html/group__DDSStringClass.html#ga13074f0132f743923a4a36ee533997fe .. _`Configuring Resource Limits`: ../../api_c/html/group__DDSUserManuals__ResourceModule.html Resource Limits =============== All resource limits in |me| are specified in a QoS policy or property. The properties listed below are where the various resource limits are applied, and section `Configuring Resource Limits`_ describes each user adjustable resource limit in more detail. See the `Micro Memory Map`_ below for an overview of the memory used by each resource limit and where they apply. DomainParticipantFactoryQos --------------------------- See `DomainParticipantFactoryQos `_ for more detail. DomainParticipantQos -------------------- The `DomainParticipantQos `_ controls resources that are applicable to the entire DomainParticipant. All the resources specified in the DomainParticipantQos are allocated when the DomainParticipant is created with the `DDS_DomainParticipantFactory_create_participant()`_ call. DataReaderQos ------------- The `DataReaderQos `_ controls the resources used by the DDS_DataReader. Each DDS_DataReader allocates its own resources, even DDS_DataReader's of the same DDS_Topic. For this reason is it advised to limit the number of DDS_DataReader's per DDS_Topic to one. DataWriterQos ------------- The `DataWriterQos `_ controls the resources allocated by a DDS_DataWriter. Each DDS_DataWriter allocates its own resources, even DDS_DataWriters of the same DDS_Topic. For this reason is it advised to limit the number of DDS_DataWriters per topic to one. OSAPI ----- See `OSAPI `_ for more details. UDP Transport ------------- See `UDP Transport `_ for more details. Dynamic Participant Static Endpoint (DPSE) ------------------------------------------ The `Dynamic Participant Static Endpoint (DPSE) `_ discovery plugin creates one DDS_DataWriter and one DDS_DataReader for the ParticipantBuiltinTopicData. The memory for the plugin includes the memory allocated by the DDS_DataReader and DDS_DataWriter. The memory allocated by the properties must be added for total memory usage. Dynamic Participant Dynamic Endpoint (DPDE) ------------------------------------------- The `Dynamic Participant Dynamic Endpoint (DPDE) `_ discovery plugin creates one DDS_DataWriter and one DDS_DataReader for each ParticipantBuiltinTopicData, PublicationBuiltinTopicData, and SubscriptionBuiltinTopicData. The memory for the plugin includes the memory allocated by these DDS_DataReaders and DDS_DataWriters. The memory allocated by the properties must be added for total memory usage. .. _`Micro Memory Map`: Memory Map ---------- .. image:: ../../images/MicroMemoryMap.png