Understanding performance considerations

Subscribers running as part of a redundant service should evaluate whether it is necessary to subscribe before the service goes Hot. To reduce the subscription load on the PubSub system, it is recommended to unsubscribe when the service goes into standby and only re-subscribe after the state goes Hot.

It is preferable to subscribe topics with no integrity when large numbers of topics are involved. This practice is particularly important when the publishers and subscribers are running on different computers. A large volume of integrity updates can flood the network, causing messages to be lost. Overloading the network will result in a cycle of additional integrity update requests, in an attempt to restore the missed data.