2.2.4. RTI Persistence Service

2.2.4.1. Persistence Service default setting changes may increase memory utilization

This release has updated the default configuration of use_wait_set in the <persistence_group> tags to TRUE, improving the performance of Persistence Service. In fact, use_wait_set has been deprecated. See Deprecation of <use_wait_set> below.

This release has also changed the default configuration of single_subscriber and single_publisher to FALSE, optimizing scalability for scenarios involving multiple concurrent applications.

Although these changes improve performance and scalability, you may notice increased memory utilization when running Persistence Service.

See Creating Persistence Groups, in the RTI Connext Core Libraries User’s Manual, for more information on these settings.

2.2.4.2. Configuration parameters for data synchronization have changed

Connext 7.5.0 introduced an improved sample synchronization protocol for redundant Persistence Service instances, configured by setting the <data_synchronization> tag in the <persistence_service><synchronization> section (see What’s New in 7.5.0 in the Persistence Service Release Notes).

In Connext 7.6.0, the configuration parameters for this protocol have changed. Specifically, the <remote_provider_change_period> tag has been removed and replaced by two new parameters: <stable_provider_period_count> and <max_remote_provider_change_period_count>. If you continue using <remote_provider_change_period>, the Persistence Service will fail to start and report an error.

For information on the new parameters and how they work, see Synchronizing of Persistence Service Instances in the RTI Connext Core Libraries User’s Manual.

2.2.4.3. Deprecation of <use_wait_set>

In release 7.6.0, Persistence Service now always uses WaitSets, to improve performance. As a result, Listener-based execution mode is deprecated, and Persistence Service will always use waitsets for reading and writing data. The <use_waitset> tag is deprecated.

While Connext still accepts the <use_waitset> tag in configuration files for backward compatibility, any value in it will be ignored, and a log message will be printed to clarify this behavior.

Most customers will not need to take any action, since <use_waitset> defaults to TRUE in 7.6.0, and in 7.5.0 and earlier it defaults to FALSE, but the new behavior will simply ignore it. However, if your configuration explicitly sets <use_waitset> to FALSE, Persistence Service will log a warning and proceed with WaitSet mode.

See the Persistence Service Release Notes for more information on this and other improvements to Persistence Service in 7.6.0. See also Creating Persistence Groups, in the RTI Connext Core Libraries User’s Manual, for more information on WaitSets in Persistence Service.