DocumentationHardware requirements
The hardware requirements for SKOOR Engine and Collector depend on several factors. The most important are:
Number of measurements per second
Number of Dashboards and Widgets: more CPU cores allow more parallel read requests
Disk size requirements mainly depend on how much data will be saved to the database. Key factors are the number of history values and history states which have to be saved. It also depends on the period for which the data should be available before it expires. Expired data will be deleted. Measurement values are stored for one year per default (adjustable).
It is advisable to discuss requirements directly with SKOOR.
Nevertheless, here are some recommendations:
Common
CPU | Intel Xeon or AMD64, 64bit architecture is required. i386 and IA64 architecture is NOT supported. At least 4 CPU cores must be present. The SKOOR Engine will not start otherwise. If running the SKOOR engine inside a virtual machine, make sure to assign the virtual CPUs on the same CPU socket (i.e. do not spread CPUs across multiple sockets) |
|---|---|
Network | Gigabit interface |
SKOOR Engine
Memory | 6 GB minimum, 8 GB for use with dashboards |
|---|---|
Disk | At least 1 disk. For better performance it is advisable to split the database filesystems for indexes and tablespaces. An advanced setup might be:
|
Standalone SKOOR Collector
Memory | 2 GB |
|---|---|
Disk | 1 disk is sufficient. Disk I/O is usually lower compared to the server |
SKOOR Engine for SNAP/SNBI
As a rule of thumb, the SKOOR system for SNAP/SNBI should be half the size of the StableNet system it is integrated with.
CPU | 16 cores |
|---|---|
Memory | 64 GB |
Disk | 1 TB |
Disk Partitioning SKOOR Server
Directory | Space required | Comment |
|---|---|---|
/opt/eranger | 100 GB |
Compressed DB backups are stored in /opt/eranger/server/backups by default. Additionally, /opt/eranger/tmp is used as temporary space for creating full database backups. If this is left unchanged then /opt/eranger needs to be at least as large as the database volume. |
/srv/eranger | 20 GB |
|
/var/log/eranger | 5 GB |
More space needed if logfiles are kept longer than defined in default settings |
/var/opt/run/eranger | 20 GB |
|
/var/lib/pgsql/ | 100 GB |
While 50 GB might be sufficient for a small system (used primarily for dashboards), medium to large systems will need at least 100 GB. Mounting the following two directories to separate disks or volumes can improve performance by up to 3 times: /var/lib/pgsql/data/ng_tblspc/idx_space/ These two directories make up most of the space taken up by the database tables and are usually about the same size, so each can be assigned half the space reserved for the database |
Disk Partitioning Standalone SKOOR Collector
Directory | Space required | Comment |
|---|---|---|
/opt/eranger | 20 GB |
|
/var/log/eranger | 1 GB |
More space needed if logfiles are kept longer than defined in default settings |
/var/opt/run/eranger | 20 GB |
|
Disk Partitioning SKOOR Server for StableNet SNAP / SNBI
Directory | Space required | Comment |
|---|---|---|
/opt/eranger | 50 GB | See above. Due to the fact that SNBI/SNAP systems do not use SKOOR measurements, backups of the SKOOR database will be small |
/srv/eranger | - | Very little data expected on this filesystem |
/var/log/eranger | 5 GB | See above |
/var/opt/run/eranger | 20 GB | See above |
/var/lib/pgsql/ | 1 TB | Due to the fact that a big amount of data is expected in the StableNet related database, consider a suitable backup strategy:
|