Fix performance issues after the fact

Remedying performance issues as they occur involves monitoring subscriptions for data change rates. If your system begins to slow down or starts to show communication failures or bad quality data on subscribed attributes, do the following:

• Create a new ASBMxDataProvider service instance on the publishing side

• Configure the new service instance

• Assign the new service instance to a node and deploy it

  Perform the operation on any node in the multi-galaxy environment exhibiting performance issues.

In a smaller multi-galaxy environment, or when you are just starting to implement multi-galaxy communication, this approach can have the advantage of saving up front configuration time, and can also serve as a trial period to gather metrics about your system.

The disadvantages of this approach are that you can lose time dealing with a system that is slowing down at run time.