DDS_SystemResourceLimitsQosPolicy Struct Reference
[SYSTEM_RESOURCE_LIMITS]

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

List of all members.

Public Attributes
DDS_Long	max_objects_per_thread
	The maximum number of objects that can be stored per thread for a DDSDomainParticipantFactory.

---

Detailed Description

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

This QoS policy is an extension to the DDS standard.

Entity:

DDSDomainParticipantFactory

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 DDSDomainParticipant entities. This QoS policy sets a parameter that places an effective upper bound on the maximum number of DDSDomainParticipant entities that can be created in a single process/address space.

---

Member Data Documentation

DDS_Long DDS_SystemResourceLimitsQosPolicy::max_objects_per_thread

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

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 DDSDomainParticipant 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 DDSDomainParticipant entities.

[range] [1, 1 billion]