System Requirements

XPLG supports various deployment architectures, ranging from a single, large standalone server to distributed clusters of smaller machines. Choosing the optimal architecture depends on the specific use case and data volume. Based on our experience, a balanced approach using medium-to-large machines offers the best trade-off between performance and manageability, avoiding the complexity of handling numerous nodes.

There is no one-size-fits-all formula, as XPLG serves a wide variety of use cases. This guide provides key recommendations and technical considerations to help optimize your deployment.

For small-scale or evaluation environments (e.g., data volume under 5 GB/day), a standard workstation or laptop may suffice. However, production deployments require careful planning around system resources, OS configuration, and network design.

Supported Operating Systems (standalone installation)

XPLG supports the following 64-bit operating systems for standalone installations:

• Linux: Kernel version 2.6.x and later (x86_64 only)

• Windows Server: 2012 and newer (x86_64 only)

• macOS: Version 11 and newer

Memory and JAVA Configuration

Memory is a critical resource for XPLG, as aggregations and in-memory data structures are heavily utilized. Recommendations include:

• Recommended RAM:

  • 32-128 GB for production

  • Avoid using less than 16 GB due to performance limitations

• Java Version: Java 17 is required.

• Memory Allocation Guidelines:

  • Linux: Allocate ~60% of total memory to the XPLG process.

  • Windows: Allocate ~70% of total memory to the XPLG process.

  • Maximum Heap Size: Do not allocate more than 32 GB to a single XPLG process, as this may degrade JVM garbage collection performance and CPU efficiency.

Note: Minimize memory swapping by lowering the OS's swappiness parameter to improve performance.

Supported Browsers

XPLG is compatible with the following browsers:

• Google Chrome (v105 or later) – Recommended

• Mozilla Firefox (v105 or later)

• Microsoft Edge (v105 or later)

Note: Microsoft Internet Explorer is no longer supported.

Required Network Ports

To ensure proper functionality of XPLG, make sure the following ports are open and accessible according to their respective directions:

🔽 Inbound Ports

These ports should be open to allow incoming connections to the XPLG server(s).

🔼 Outbound Ports

These ports are used by XPLG to initiate outbound connections to external systems.

Hardware Recommendations

CPU

Use modern multi-core processors. XPLG benefits more from additional cores than higher clock speeds. A minimum of 4–8 cores is recommended for standalone systems.

Storage

XPLG workloads involve heavy read/write activity, especially on the UI and processing engines.

• Recommended: Nvme SSDs or high-performance disks SSD

• Avoid: Slow HDDs and RAID 5 setups

• Preferred RAID Configurations: RAID 0, 10, 01, or 0+1

• NAS: Acceptable but may introduce latency

Tip: Conduct performance tests with your data and use cases to identify bottlenecks.

Network Considerations

A fast and reliable network is essential, particularly in clustered environments.

• Recommended Bandwidth: 1 GbE or 10 GbE

• Deployment Note: Avoid distributing clusters across multiple data centers or geographical regions, as latency can impact performance.

File Descriptor Limits (Linux Only)

For Linux deployments, ensure the user running XPLG is assigned a high number of open file descriptors and process limits.

See: Post Installation Recommendations or contact support@xplg.com for assistance.

Hardware Profiles

Standard Setup

• Users: Up to 3 concurrent

• Daily Volume: <10 GB

• Specs:

  • 8 CPU cores (2.5–3 GHz)

  • 32 GB RAM

  • 64-bit OS (Linux/Windows)

Recommended Setup

• Users: Up to 5 concurrent

• Daily Volume: <10 GB

• Specs:

  • 16 CPU cores (3 GHz)

  • 64GB RAM

  • 64-bit OS (Linux/Windows)

Clustered Setup

See: System Architecture or contact support@xplg.com for assistance for guidance on cluster deployment and capacity planning.

Processor Node Recommendations

UI Node Recommendations

Note: The number of UI nodes depends on concurrent users and redundancy/load balancing requirements.