...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Overview
Resources consumption really changes between different clusters and XpoLog. Nowadays, it is possible to define very large machines or multiple small machines for applications deployment – which is preferred?
From our experience, the “rule” is medium-large machines that will balance between performance results and not too many cluster nodes to be managed.
There is no fixed formula as XpoLog is used for a wide variety of tasks. The details below will some important key notes based on our experience.
Generally, for low daily volume of data (<5 GB/Day) a laptop or standard machine is sufficient, but when it comes production deployments, there are a several recommendations to consider.
Supported Operating Systems (standalone installation)
...
30303 - HTTP client access to XpoLog web interface and communication between different XpoLog instances (can be modified if needed)
30443 - HTTPS client access to XpoLog web interface and communication between different XpoLog instances (can be modified if needed)
Syslog - TCP and/or UDP any port that is required to be used.
22 - In order to enable XpoLog to establish connections to remote machines over SSH (can be modified if needed)
25 - In order to enable XpoLog to use a SMTP server to send emails (can be modified if needed)
Alerting:
162 - In order to enable XpoLog to send SNMP traps (can be modified if needed)
7676 - In order to enable XpoLog to send JMS messages (can be modified if needed)
389 - In order to enable XpoLog to authenticate users against an Active Directory (can be modified if needed)
636 - In order to enable XpoLog to authenticate users against an Active Directory through a secured connection
JDBC - In case XpoLog is planned to connect to databases using JDBC drivers, it is mandatory to open the relevant ports:
Oracle - 1521 (can be modified if needed)
MSSQL - 1433 (can be modified if needed)
MySQL - 3306 (can be modified if needed)
DB2 - 50000 (can be modified if needed)
Postgres - 5432 (can be modified if needed)
Windows Only:
135-139, 445 - Share and UNC access to remote servers
Hardware Recommendations
CPUs
You should choose a modern processor with multiple cores. Standard machines running XpoLog utilize 4-8 cores.
If you need to choose between faster CPUs or more cores, choose more cores.
Disks
Disks are important for XpoLog - XpoLog processing engines mostly perform write operations but not only, while XpoLog UI engines mostly perform read operations but not only.
XpoLog does many bulk reads/writes and many disk seeks and as disks are usually the slowest subsystem in a server, they easily become the bottleneck of the XpoLog cluster.
If you can afford SSDs, they are by far superior to any spinning media. If SSD is not an option, try to obtain the fastest disks possible (high-performance server disks, 15K RPM).
Network Attached Storage (NAS) is optional but note that NAS is often slower and displays larger latency. RAID 0, 10, 01, 0+1 will give the best performance, while RAID 5 will offer the worst performance.
...
Note: In Linux deployments, it is mandatory to allocate a high number of open files and processes to the user that runs XpoLog - for more information please see Post Installation Recommendations or contact support@xplg.com for more details.
Network
A fast and reliable network is obviously important to performance in a distributed system. Modern data-center networking (1 GbE, 10 GbE) is sufficient for most clusters.
From our experience it is recommended to avoid clusters that are distributed over multiple data centers / geographical locations
General Recommendations
Standard
The following is hardware recommendation for up to 3 concurrent users, and < 10 GB of daily logs volume:
...