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 deployment templates options was selected , depending on the size of your monitored environment. The choice determined how certain resources were allocated, and subsequent hardware requirements:
| Deployment Template | Elements | Minimum RAM | Minimum CPU Type | |||
|---|---|---|---|---|---|---|
| < 200 | 8 | Small | <100 | 2 GB | 2-core CPU | |
| Medium | 250–1000 | 16 GB | 6-core CPU | |||
| 4-cores/vCPUs | ||||||
| 201 - 1000 | 32 GB | 8-cores/vCPUs | ||||
| 1001 - 5000 | 128 GB | 24-cores/vCPUs | Large | 1000+ | 32 GB | 12-core CPU |
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.
Each deployment template sizing example ensures the underlying configurations (for example, for the bundled MySQL database and JRE) match the likely resource demands to generate reports, dashboards, and perform queries. The following summarizes these configurations:
| Configuration Parameter | Small | Medium | < 200 Elements | 201 - 1000 Elements | 1001 - 5000 ElementsLarge |
|---|---|---|---|---|---|
| MySQL buffer pool size | 120 MB | 2 GB | 4 GB | ||
| MySQL log file size | 20 MB | 512 MB | 1 GB | ||
| MySQL maximum open connections | 151 | 201 | 301 | ||
| Java heap size | 1 GB | 2 GB | 4 GB | ||
| service threads | 50 | 100 | 200 | ||
| Data Collector maximum open connections | 100 | 150 | 250 | ||
| up.time Controller heap size | 512 MB | 1 GB | 2 GB |
Modifying the
...
Sizing Examples
After initial installation, if you need to accommodate a larger number of monitored Elements, you can manually change the deployment templates sizing examples using one of two methods:
...
| Configuration Parameter | Configuration File and Location (relative to the up.time directory) | Parameter Name | Default Deployment Sizing Values | |
|---|---|---|---|---|
| MySQL buffer pool size | /mysql/my.ini | innodb_buffer_pool_size= |
| |
| MySQL log file size | /mysql/my.ini | innodb_log_file_size= | 20M512M1G | |
| MySQL maximum open connections | /mysql/my.ini | max_connections= | 151201301 | |
| Java heap size | Linux: Windows: | Linux: Windows: | Linux: | Windows: |
| service threads | /uptime.conf | serviceThreads= | 50100200 | |
| Data Collector maximum open connections | /uptime.conf | connectionPoolMaximum= | 100150250 | |
| up.time Controller heap size | Linux: Windows: | Linux: Windows: | -Xmx512m-Xmx1024m-Xmx2048m | |
The recommended option to change a deployment template sizing example is to use the sample configuration files that are found in the <uptimeInstall>/sample directory as a starting point. This option moves you to a different deployment template sizing example in the least amount of steps.
...