RTI Connext .Net APIs
Version 5.3.1
|
<<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...
#include <managed_infrastructure.h>
Static Public Member Functions | |
static System::String ^ | get_systemresourcelimits_qos_policy_name () |
Stringified human-readable name for DDS::SystemResourceLimitsQosPolicy. More... | |
Public Attributes | |
System::Int32 | max_objects_per_thread |
The maximum number of objects that can be stored per thread for a DDS::DomainParticipantFactory. More... | |
<<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).
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.
System::Int32 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]