System Requirements

Overview

XPLG supports a wide range of deployment architectures—from a single standalone instance to fully distributed, high-availability clusters.

The optimal system configuration depends on:

• Daily data ingestion volume

• Retention requirements (hot and cold)

• Concurrency (active users, dashboards, queries)

While smaller environments can run on a single machine, production deployments require careful planning of compute, storage, and network resources.

Based on field experience, a balanced architecture using medium-to-large nodes provides the best trade-off between performance, scalability, and operational simplicity.

Supported Operating Systems

Linux (Recommended)

• Modern enterprise Linux distributions Examples:

  • RHEL 9 and above

  • Ubuntu 20.04 / 22.04 / 24.04 LTS

• Kernel: 3.x and above

• Architecture: x86_64

Windows Server

• Windows Server 2016 and newer

macOS (for evaluation / non-production)

• macOS 12 (Monterey) and newer

Runtime & Dependencies

• Python (Linux only): Python 3.12 or newer

• Docker (optional deployments): Docker 29+

Memory & JVM Configuration

Memory is a critical resource for XPLG due to heavy use of in-memory processing and aggregations.

Recommended RAM

• Production: 32–128 GB

• Minimum: 16 GB (not recommended for production)

Memory Allocation

• Linux: allocate ~60% of system memory

• Windows: allocate ~70% of system memory

JVM Guidelines

• Maximum heap size per process: ≤ 32 GB

• Avoid excessive heap allocation to prevent GC degradation

OS Optimization

• Reduce Linux swappiness to minimize memory swapping

CPU Requirements

• Use modern multi-core CPUs

• XPLG benefits more from core count than clock speed

Recommended

• Standalone: 8–16 cores

• Production / cluster nodes: 16–32+ cores

Storage Requirements

XPLG workloads are I/O intensive, especially for indexing and query operations.

Recommended

• NVMe SSD (preferred) or high-performance SSD

Avoid

• Slow HDDs

• RAID 5 (write penalty)

Preferred RAID Configurations

• RAID 0 / 10 / 01

Notes

• NAS is supported but may introduce latency

• Storage sizing is directly tied to:

  • Daily volume

  • Retention period

Network Requirements

• Recommended: 1 GbE minimum, 10 GbE preferred for clusters

• Low latency is critical for distributed deployments

Important

• Avoid distributing cluster nodes across multiple regions / data centers, as latency impacts performance

Supported Browsers

XPLG supports modern, evergreen browsers:

• Google Chrome (latest stable) – Recommended

• Mozilla Firefox (latest stable)

• Microsoft Edge (latest stable)

❗ Internet Explorer is not supportedRequired Network Ports

File Descriptor Limits (Linux)

Ensure high limits for:

• Open files (64,000+)

• Processes (20,000+)

This is critical for high-ingestion environments.

Network Ports

🔽 Inbound Ports (to XPLG)

🔼 Outbound Ports (from XPLG)

Deployment Profiles (Guidelines)

Small / Evaluation

• < 5–10 GB/day

• 16 CPU cores, 32 GB RAM

Standard Production

• < 10 GB/day

• 16 CPU cores, 64 GB RAM

Clustered Environments

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 capacity planning.

Processing Nodes

UI Nodes

Note: UI node scaling should align with concurrency levels and HA requirements. Environments with high user activity or strict availability requirements should deploy multiple UI nodes with load balancing to ensure performance, redundancy, and fault tolerance.