Ignition Server load

Ignition
1

Hi team,

I want to implement a standard-redundant Ignition SCADA system that will read data from 337 solar inverters, distributed across twelve Sungrow data loggers. From each inverter, approximately 90 analog points will be read, using Modbus TCP/IP every 3 seconds.

The plan is to historize the data using the Ignition Historian module, writing to a MySQL database. At least 10 points per inverter will be historized every 5 seconds, while the remaining points will be historized on-change or using deadband.

The configuration I normally use is a single server where all Ignition modules are installed, along with the database. In this case, the system will be Ignition redundant. The clients (at least 2) will run on separate PCs.

My question is whether that amount of Modbus driver polling and database access from the historian can be handled by a standard Ignition installation.

Server characteristics:

  • HPE ProLiant DL380 Gen11

  • Intel Xeon Silver 4514Y — 16 cores, 2.0 GHz

  • 64 GB RAM

  • RAID 5 with approximately 1.8 TB storage

  • Dual power supply

  • Same hardware for both servers in the redundant pair

Ignition 8.3

Windows Server 2025

Mysql database

2

Don’t do this for starters.

1 Like
3

To clariy… Move the database to another dedicated server so it’s not competing with Ignition for resources.

3 Likes
4

And so you can deploy the database's redundancy support separately from Ignition. An Ignition database connection to localhost cannot be redundant.