Groundplex requirements: Hardware and OS

Hardware requirements

A Groundplex is a local server running on hardware that you provision. The hardware must meet the following minimum requirements.

Nodes Minimum value: 1

Recommended: 2 or more nodes

SnapLogic Project and Enterprise platform package nodes can be configured in the following sizes:
  • Medium: 2 vCPU and 8GB RAM 
  • Large: 4 vCPU and 16GB RAM 
  • X-Large: 8 vCPU and 32GB RAM
  • 2X-Large: 16 vCPU and 64GB RAM

SnapLogic recommends two nodes for high availability. For requirements about clustering nodes, see Node Cluster.

Important: All nodes within a Snaplex must be of the same size.
RAM Minimum value: 8GB Depending on the size, number, and nature of pipelines, more memory (RAM) might be required to maintain an acceptable level of performance. The memory used depends the volume and size of the documents being processed.  Some Snaps, like the Sort Snap, hold many documents in memory during processing and, therefore, consume more memory.
Note: Contact your SnapLogic Sales Engineer to perform an optimum-sizing analysis based on your requirements.
CPU Minimum value: 2 cores All Snaps execute in parallel in their own threads; therefore, the more cores that are available to the Snaplex, the more performant the system.
Disk Space Minimum value: 40GB

Recommended: 100GB

Local disk space is required for logging and for any Snap that uses the local disk for temporary storage, such as the Sort and Join Snaps. For details, see Temporary Folder.
Note: SnapLogic does not restrict the disk size of your Groundplex nodes.

Operating Systems

The following operating systems are supported for SnapLogic Groundplexes:
  • Linux:
    • CentOS 6.3 or newer
    • Red Hat
    • Debian
    • Ubuntu 14.04 or newer
  • Windows Server 2016/2019/2022 with a minimum of 8GB RAM.
For improved security, the Groundplex machine timestamp is verified to check if it is in sync with the timestamp on the SnapLogic cloud. Running a time service on the Groundplex node will ensure that the timestamp is always kept in sync.

Large clock differences can also affect communication between the FeedMaster and the JCC nodes. The expression language function might be different between Snaplex nodes, and Internal log messages might have skewed timestamps, making it more difficult to debug issues.