OPC UA Subscription Performance

OPC UA Subscription Performance

animation
opc-ua
iiot
Try Change Variables per batched message to compare overhead. Then press Calculate bandwidth.
Observe After pressing Calculate bandwidth, watch total bandwidth savings as Dead-band filtering reduction (%) changes.
Explain Explain why Publishing interval (ms) changes notifications/sec after you press Calculate bandwidth.

Technical boundaries. The calculator uses 24 bytes per message header and an assumed filtering reduction. Validate dead-band and queue settings with actual process data so significant changes are not suppressed.

Use this interactive calculator to understand how subscription parameters affect bandwidth and data volume in your OPC-UA deployment.

TipInterpretation Guide

Dead-band filtering eliminates noise by only reporting changes exceeding a threshold (e.g., temperature >0.5°C> 0.5°C change). For process variables that fluctuate within tolerance, this can reduce notifications, but changes inside the configured deadband are not sent to subscribers; retain raw history separately when it is needed.

Batching aggregates multiple variable updates into single messages, reducing per-message overhead. Instead of 24 bytes overhead per variable, batching 10 variables means 24/10=2.424/10 = 2.4 bytes overhead each.

Typical use: Treat the calculator as a sizing aid, then validate the chosen dead-band and queue settings with actual process data so significant changes are not suppressed.

Back to the chapter