CitectSCADA Virtualized Environment

This is very true. Also, some IT staff don't understand the inner workings of CitectSCADA. Unfortunately it is essentially still a single thread application, so it benefits more from having high clock speeds rather than the number of CPUs. IT usually think they can fix application performance by throwing more vCores or RAM at it, but this will not work with Citect.

I find that Citect runs great on small-office servers that have only a few CPU cores and high clock speeds, and performs a lot less on the standard infrastructure that IT uses for virtualization of office applications. For the most demanding Citect projects we use dedicated hardware with just one or two VMs running on it. Virtualization is then only used for the ease of maintenance (hardware upgrades).

If you want to run your whole OT environment on a single (redundant) server with many CPU cores, you may end up buying very expensive CPUs.

This is very true. Also, some IT staff don't understand the inner workings of CitectSCADA. Unfortunately it is essentially still a single thread application, so it benefits more from having high clock speeds rather than the number of CPUs. IT usually think they can fix application performance by throwing more vCores or RAM at it, but this will not work with Citect.

I find that Citect runs great on small-office servers that have only a few CPU cores and high clock speeds, and performs a lot less on the standard infrastructure that IT uses for virtualization of office applications. For the most demanding Citect projects we use dedicated hardware with just one or two VMs running on it. Virtualization is then only used for the ease of maintenance (hardware upgrades).

If you want to run your whole OT environment on a single (redundant) server with many CPU cores, you may end up buying very expensive CPUs.