Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »


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 must properly tune your JVM heap size.

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

    • Heap size 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 the amount of space.

    • Open JDK is recommended but you can also use Java 11

  2. Another important aspect to consider is that the historian is mostly limited by I/O performance (speed of disk drive). Using a 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 Folio's highly efficient compression techniques. Analysis of projects has shown an average about 1.5 bytes per timestamp sample which equates to about 51KB per year per point for 15min interval data.

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

    • curVal synchronization and his collection typically requires a high amount of bandwidth and CPU processing

    • batch synchronization of history data is typically far more efficient and easier to tune than curVal synchronization

    • how many programs/alarms is will have a big impact on CPU processing

    • running multiple projects on a single host consumes more overhead; 100 little projects of 100 points requires more horse power than a single 10K point project

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

    • How points get into a watch:

      • Trend (Always)

      • Programs (Always)

      • Alarms (Always)

      • Graphics (On View Only)

      • Point Graphics (On View Only)

      • Summaries (On View Only)

  5. Database limits

    • Maximum 300 connectors per FIN instance

    • Maximum 2000 items per tree

  • No labels