Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Recommendation

CPU

Modern x86-64 CPU (Intel Xeon, Intel Core, AMD Ryzen)

Operating System

Windows, Linux, Mac

CPU Power

2GHz+

RAM

4GB (8-16GB+ Recommended)

Flash

32GB SSD

Interface

Gigabit LAN

Project Sizing: 

  1. RAM (Most IMPORTANT for Sizing):

    • The most important resource for server sizing is RAM. For any medium to large project, you , which must properly tune your JVM heap size for any medium to a large project.

    • A good rule of thumb is to plan for 1GB to 2GB of heap for every 10K points.

    • Heap size of more than 1.5GB will need to run a 64-bit JVM (the actual max heap size of a 32-bit JVM will vary slightly).

    • 85% of Java Heap consumption is roughly our recommended max before considering to upgrade upgrading the amount of space.

    • Open JDKis recommended, but you can also use Java 11

  2. Another important aspect to consider is that the historian is mostly limited mainly by I/O performance (speed of disk drive speed). Using a an SSD will likely have a significant performance boost for reading and writing history data. Disk space is typically not a issue for projects due to the Due to Folio's highly efficient compression techniques, disk space is typically not an issue for projects. Analysis of projects has shown an average of about 1.5 bytes per timestamp sample which equates to about 51KB per , equating year per point for 15min interval data.

  3. Depending on the apps/features you use (and don't use) will have a significant significantly impact on performance and how much horsepower you will need to run smoothly.

  4. Max amount of points that should be in the watch at one time should be around 50k

  5. Database limits