Sizing varies based on the number of monitors per element, the type of objects monitored, and the method used to gather performance data. up.time recommendations are based on an average of 2 or 3 monitors per element.
During up.time's installation, one of three options was selected depending on the size of your monitored environment. The choice determined how certain resources were allocated, and subsequent hardware requirements:
| Elements | Minimum RAM | Minimum CPU Type |
|---|---|---|
| < 200 | 8 GB | 4-cores/vCPUs |
| 201 - 1000 | 32 GB | 8-cores/vCPUs |
| 1001 - 5000 | 128 GB | 24-cores/vCPUs |
As a general rule of thumb when planning the allocated disk space, you should plan on allocating about 4 GB per monitored element. Note that per element usages are per year, unless you archive using old data.
...
| Configuration Parameter | Configuration File and Location (relative to the up.time directory) | Parameter Name | Default Sizing Values | |
|---|---|---|---|---|
| MySQL buffer pool size | /mysql/my.ini | innodb_buffer_pool_size= |
| |
| MySQL log file size | /mysql/my.ini | innodb_log_file_size= | 20M 512M 1G | |
| MySQL maximum open connections | /mysql/my.ini | max_connections= | 151 201 301 | |
| Java heap size | Linux: Windows: | Linux: Windows: | Linux: | Windows: |
| service threads | /uptime.conf | serviceThreads= | 50 100 200 | |
| Data Collector maximum open connections | /uptime.conf | connectionPoolMaximum= | 100 150 250 | |
| up.time Controller heap size | Linux: Windows: | Linux: Windows: | -Xmx512m -Xmx1024m -Xmx2048m | |
...