OPC UA Subscription Performance
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.
Calculate bandwidth
Reset
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.
viewof numVariables = Inputs. range ([100 , 10000 ], {
value : 2000 ,
step : 100 ,
label : "Number of variables"
})
viewof publishingInterval = Inputs. range ([50 , 5000 ], {
value : 100 ,
step : 50 ,
label : "Publishing interval (ms)"
})
viewof bytesPerNotification = Inputs. range ([16 , 128 ], {
value : 32 ,
step : 8 ,
label : "Bytes per notification"
})
viewof deadbandReduction = Inputs. range ([0 , 95 ], {
value : 75 ,
step : 5 ,
label : "Dead-band filtering reduction (%)"
})
viewof batchSize = Inputs. range ([1 , 50 ], {
value : 10 ,
step : 1 ,
label : "Variables per batched message"
})
baseNotificationsPerSec = numVariables / (publishingInterval / 1000 )
baseBytesPerSec = baseNotificationsPerSec * bytesPerNotification
baseGBPerDay = (baseBytesPerSec * 86400 ) / (1024 * 1024 * 1024 )
// After dead-band filtering
filteredNotificationsPerSec = baseNotificationsPerSec * (1 - deadbandReduction / 100 )
filteredBytesPerSec = filteredNotificationsPerSec * bytesPerNotification
filteredGBPerDay = (filteredBytesPerSec * 86400 ) / (1024 * 1024 * 1024 )
// Message overhead (24 bytes per message header)
messageOverhead = 24
variablesPerMessage = batchSize
bytesPerVariableWithOverhead = bytesPerNotification + (messageOverhead / variablesPerMessage)
// After batching
batchedBytesPerSec = filteredNotificationsPerSec * bytesPerVariableWithOverhead
batchedGBPerDay = (batchedBytesPerSec * 86400 ) / (1024 * 1024 * 1024 )
// Savings
bandwidthSavings = ((baseGBPerDay - batchedGBPerDay) / baseGBPerDay) * 100
html `<div style="background: #f8f9fa; border-left: 4px solid #16A085; padding: 15px; margin: 20px 0; border-radius: 4px; font-family: Arial, sans-serif; overflow-x: auto;">
<div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)); gap: 20px; margin-bottom: 15px;">
<div style="background: white; padding: 15px; border-radius: 4px; box-shadow: 0 2px 4px rgba(0,0,0,0.1);">
<div style="font-size: 12px; color: #7F8C8D; text-transform: uppercase; margin-bottom: 5px;">Base Rate (Unoptimized)</div>
<div style="font-size: 24px; font-weight: bold; color: #E74C3C;"> ${ baseNotificationsPerSec. toFixed (0 )} notifications/sec</div>
<div style="font-size: 14px; color: #2C3E50; margin-top: 5px;"> ${ baseGBPerDay. toFixed (1 )} GB/day</div>
</div>
<div style="background: white; padding: 15px; border-radius: 4px; box-shadow: 0 2px 4px rgba(0,0,0,0.1);">
<div style="font-size: 12px; color: #7F8C8D; text-transform: uppercase; margin-bottom: 5px;">After Dead-band</div>
<div style="font-size: 24px; font-weight: bold; color: #E67E22;"> ${ filteredNotificationsPerSec. toFixed (0 )} notifications/sec</div>
<div style="font-size: 14px; color: #2C3E50; margin-top: 5px;"> ${ filteredGBPerDay. toFixed (1 )} GB/day</div>
</div>
<div style="background: white; padding: 15px; border-radius: 4px; box-shadow: 0 2px 4px rgba(0,0,0,0.1);">
<div style="font-size: 12px; color: #7F8C8D; text-transform: uppercase; margin-bottom: 5px;">Fully Optimized</div>
<div style="font-size: 24px; font-weight: bold; color: #16A085;"> ${ filteredNotificationsPerSec. toFixed (0 )} notifications/sec</div>
<div style="font-size: 14px; color: #2C3E50; margin-top: 5px;"> ${ batchedGBPerDay. toFixed (1 )} GB/day</div>
</div>
</div>
<div style="background: white; padding: 15px; border-radius: 4px; box-shadow: 0 2px 4px rgba(0,0,0,0.1); text-align: center;">
<div style="font-size: 14px; color: #7F8C8D; margin-bottom: 5px;">Total Bandwidth Savings</div>
<div style="font-size: 32px; font-weight: bold; color: #16A085;"> ${ bandwidthSavings. toFixed (1 )} %</div>
<div style="font-size: 14px; color: #2C3E50; margin-top: 5px;"> ${ (baseGBPerDay - batchedGBPerDay). toFixed (1 )} GB/day reduction</div>
</div>
<div style="margin-top: 15px; padding: 10px; background: #E8F8F5; border-radius: 4px; font-size: 13px; color: #2C3E50;">
<strong>Optimization Breakdown:</strong><br/>
• Dead-band filtering reduces notifications by ${ deadbandReduction} % ( ${ (baseGBPerDay - filteredGBPerDay). toFixed (1 )} GB/day saved)<br/>
• Batching ${ batchSize} variables/message reduces overhead from ${ messageOverhead} to ${ (messageOverhead / batchSize). toFixed (1 )} bytes/variable<br/>
• Final rate: ${ (batchedBytesPerSec / 1024 ). toFixed (1 )} KB/sec average bandwidth
</div>
</div>`
Dead-band filtering eliminates noise by only reporting changes exceeding a threshold (e.g., temperature > 0.5 ° C > 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.4 24/10 = 2.4 24/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