# Ignition Server load **URL:** \ **Category:** Ignition\ **Created:** [February 24, 2026, 10:32pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156 "2026-02-24T22:32:02Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![denny\_jimenez](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@denny\_jimenez](https://forum.inductiveautomation.com/u/denny_jimenez)\ **Post date:** [February 24, 2026, 10:32pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/1 "2026-02-24T22:32:02Z")
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 ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [February 24, 2026, 10:34pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/2 "2026-02-24T22:34:44Z")
> [@denny\_jimenez](#): > > a single server where all Ignition modules are installed, along with the database. Don’t do this for starters. ---
**Author:** ![Lynn\_Martineau](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@Lynn\_Martineau](https://forum.inductiveautomation.com/u/Lynn_Martineau)\ **Post date:** [February 24, 2026, 10:57pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/3 "2026-02-24T22:57:55Z")
To clarify… Move the database to another dedicated server so it’s not competing with Ignition for resources. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 25, 2026, 12:17am UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/4 "2026-02-25T00:17:57Z")
And so you can deploy the database's redundancy support separately from Ignition. An Ignition database connection to `localhost` **cannot** be redundant. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [February 25, 2026, 1:34pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/5 "2026-02-25T13:34:43Z")
> [@denny\_jimenez](#): > > From each inverter, approximately 90 analog points will be read, using Modbus TCP/IP every 3 seconds. I believe a large portion of your success will be based on how many requests (per device) are needed to retrieve the data you require, and how much (er, little) latency exists between the server(s) and devices. From my experience, I’ve little concern with this amount of database throughput. Are you able to deploy a test server on the solar network? Build a device, build and instantiate a UDT, then monitor device status to determine if the driver will sufficiently optimize requests, and if the network will support your goal. After you have one device & tag configured, script the generation of all others…and **try** it? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 25, 2026, 1:51pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/6 "2026-02-25T13:51:54Z")
> [@Chris\_Bingham](#): > > script the generation of all others FWIW, my Spreadsheet import tool was built for a solar integration doing exactly this type of device and UDT instantiation. ---
**Author:** ![denny\_jimenez](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@denny\_jimenez](https://forum.inductiveautomation.com/u/denny_jimenez)\ **Post date:** [February 25, 2026, 2:51pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/7 "2026-02-25T14:51:30Z")
Hi Chris, We're currently in the design phase; we can't have a test until the launch. But I agree that I don't foresee any problems with that size database. Thanks. ---
**Author:** ![denny\_jimenez](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@denny\_jimenez](https://forum.inductiveautomation.com/u/denny_jimenez)\ **Post date:** [February 25, 2026, 2:53pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/8 "2026-02-25T14:53:30Z")
Thanks Phil, Excellent tool, I'll definitely use it. Thanks for the info. Another question: is it possible to manage the historical database on a NAS, for example, where we can use MySQL? Thanks ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 25, 2026, 3:20pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/9 "2026-02-25T15:20:30Z")
> [@denny\_jimenez](#): > > historical database on a NAS Yes, but keep in mind that databases are RAM and CPU intensive when supporting long history trend charting. ---
**Author:** ![denny\_jimenez](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@denny\_jimenez](https://forum.inductiveautomation.com/u/denny_jimenez)\ **Post date:** [February 25, 2026, 3:44pm UTC](https://forum.inductiveautomation.com/t/ignition-server-load/114156/10 "2026-02-25T15:44:43Z")
Thanks Phil.