To move the server load for subscription-based reading from CPU to RAM usage, make the following settings:

  • Increase the publishing interval of the subscription and the maximum number of messages stored in the queue for the monitored item on the OPC UA client side

    or

  • Reduce the corresponding values on the ibaHD-Server side in the MaxMessageSize, MaxMessageQueueSize and MinPublishingInterval fields for all clients, see Preferences.

Data is lost

If data or values are lost during subscription-based reading, try reducing the subscription's publishing interval or increasing the number of messages stored in the queue. Note that the OPC UA Server module moves all queried values in a publishing interval to the queue.
Problems when requesting large amounts of raw data

If you request large amounts of raw data via historical functions, problems may occur due to the default limitation of 1 megabyte per message on the OPC UA side. You can adjust the limit to up to 10 megabytes in the preferences in intelligent mode and to any value in extended mode. Please note the possible effects on the network.

See .