DDS_SystemResourceLimitsQosPolicy Struct Reference

<<extension>> Configures DDS_DomainParticipant-independent resources used by RTI Connext. Mainly used to change the maximum number of DDS_DomainParticipant entities that can be created within a single process (address space). More...

Data Fields
DDS_Long	max_objects_per_thread
	The maximum number of objects that can be stored per thread for a DDS_DomainParticipantFactory.

Detailed Description

<<extension>> Configures DDS_DomainParticipant-independent resources used by RTI Connext. Mainly used to change the maximum number of DDS_DomainParticipant entities that can be created within a single process (address space).

Entity:

DDS_DomainParticipantFactory

Properties:

RxO = N/A
Changeable = NO

Usage

Within a single process (or address space for some supported real-time operating systems), applications may create and use multiple DDS_DomainParticipant entities. This QoS policy sets a parameter that places an effective upper bound on the maximum number of DDS_DomainParticipant entities that can be created in a single process/address space.

Field Documentation

DDS_Long DDS_SystemResourceLimitsQosPolicy::max_objects_per_thread

The maximum number of objects that can be stored per thread for a DDS_DomainParticipantFactory.

Before increasing this value to allow you to create more participants, carefully consider the application design that requires you to create so many participants. Remember: a DDS_DomainParticipant is a heavy-weight object. It spawns several threads and maintains its own discovery database (see DISCOVERY). Creating more participants than RTI Connext strictly requires – one per domain per process/address space – can adversely affect the performance and resource utilization of your application.

[default] 1024; this value allows you to create about 10 or 11 DDS_DomainParticipant entities.

[range] [1, 1 billion]