General advice:
Lots of cores - individual clock speed doesn’t matter nearly as much. Java, and therefore Ignition, parallelize well to multiple CPU cores. This is especially relevant if you’ll be using Perspective, because Perspective sessions have a ‘backend’ component running on the gateway to match each ‘frontend’ component running on the local device (browser, phone, workstation).
Plenty of memory. While there’s lots of FUD about how memory hungry Java is, it’s not entirely without merit. As Phil mentioned - keeping your DB separate from your Ignition instance is generally considered good practice, so that they aren’t fighting over the host’s memory.
Good disk speed. This isn’t very unique to Ignition, but especially in Ignition 8.0 and up, now that project resources are literally files on disk, high read speeds (i.e., some kind of SSD, over a spinning-disk) are going to pay dividends. Actual capacity on that disk is not likely to be a big deal - Ignition itself takes up just over a gigabyte, but that’s almost entirely the different runtimes we bundle for Windows, Linux, and MacOS. Your actual Ignition configuration is almost certainly going to be in the tens of megabytes - over 100 megabytes is probably the 99th percentile of gateway backups.
4 Likes