[QUESTION] Maximizing Fuxa's Capacity: Seeking Insights on Tags, Hardware, and Concurrent Users

[mauroalexandre]

Hello!
We are currently in the requirements gathering phase and have encountered a question regarding the maximum capacity for tags and concurrent users that Fuxa can support.

Could you share your experiences regarding the largest project you've managed with Fuxa, specifically noting:

• The number of tags
• The hardware used
• The number of concurrent users

Your insights would be invaluable. Thank you!

[mauroalexandre]

In my case

Devices: 1 Tags: 477 Hardware: i3-12100, 8GB RAM, SSD 256 Concurrent users: 1

[MatthewReed303]

RPI CM4 64bit, running Fuxa, CodeSys, Node-Red, Databases etc currently 1000 Tags via OPC-UA, has VPN and reverse proxy and web clients including 2x onsite clients. The project will grow by another 1000+ tags next year when I upgrade next section of the plant and add large database and batching etc

Devices: 1 Tags: 1000+ Hardware: RPI CM4 64bit, 4GB Ram, 32GB EMMC, 128GB NVMe Concurrent users: 2+

[robsori]

I tested consecutively, through simulations with the connection to a local OPC UA server (on the same PC):

Tags: 1024 Device: 1 Hardware: i3, 8 GB RAM, SSD 128 Connection: OPC UA Concurrent users: 1

Tags: 2048 Device: 1 Hardware: i5, 8 GB RAM, SSD 256 Connection: OPC UA Concurrent users: 1

Tags: 4096 Device: 1 Hardware: i5, 8 GB RAM, SSD 256 Connection: OPC UA Concurrent users: 1

I noticed that the more the number of tags increases, the more difficult it is to configure the project. Increasing the hardware resources, the work becomes proportionally easier. If you disable the connection, to stop reading the data, the configuration mode becomes easier even if there are many tags.