Performance Analysis
This chapter compiles four sets of measurement data. Each describes its setup, the hardware used, and the measured values; the project files are available for download.
| Measurement Series | Scenario | Key Metrics | Measured with |
|---|---|---|---|
| BatchRead every 30 seconds | 640,000 OPC data points are read every 30 seconds via four OPC UA connections and transmitted to MQTT and InfluxDB | 21,209 data points/s | OPC Router 5.3.5007.156 |
| Multi-Data-Change Trigger | 32,000 tags are monitored for value changes via 160 template instances and transferred to MQTT and InfluxDB | approximately 28,500 data points/s | OPC Router 5.3.5008.157 |
| transfer object | Batch Read versus OPC Data Access, each with Cron, data change, and time triggers, pushed to the performance limit | more than 19,500 tags/s | OPC Router 5.3.5008.157 |
| MQTT Publish | Message throughput against a Mosquitto broker, with and without connection pooling, for QoS levels 0, 1, and 2 | 5,556 messages/s | OPC Router 5.5 |
All measurement series were collected using older product versions; no new measurements are available for version 5.7.
Disclaimer Regarding Performance Analysis
The benchmark results and test results presented in this documentation were collected under specific conditions. Actual performance in a productive environment may vary significantly depending on numerous factors, including, but not limited to:
- Server hardware (processor performance, RAM, memory type and speed, number of cores, cache size, CPU clock speed)
- Network infrastructure (bandwidth, latency, network topology, firewalls, load balancers)
- Operating system and configuration (kernel version, process priorities, memory management, background processes)
- Background processes and system-related load
- Storage systems (SSD vs. HDD, RAID configuration, read/write access)
- Number and type of connected third-party systems (API calls, response times of external systems)
- and much more
This performance analysis therefore serves only as a guide and cannot be interpreted as a universal statement about the performance of OPC Router under any conditions. For a reliable assessment in a specific environment, separate, customized tests are required.