Good morning everyone!
As final work for my degree thesis, I am bringing the report on the implementation and configuration of netXMS in my Company network.
Dear Admins, based on your experience would you be able to evaluate the necessary resources (CPU, RAM, DB disk space) depending on the number of clients to monitor, excluding the space required by Windows logs?
Something like:
from 1 to 100 clients: x CPU, yGB RAM, z GB DB space
from 101 to 500 clients: ...
Thank you so much for your support and the wonderful product you have developed and supported.
Fabrizio
It's quite hard to estimate required resources, as they depend not only on the number of nodes, but also on number of interfaces, number of DCIs per node, data collection interval and storage time, number of scripts, number of various events happening and so on. Also, on big systems use of Timescale DB helps, as it minimizes housekeeper resource usage.
Here are some real-life data about tree installations - X, Y and Z. All are using SSD or NVMe storage. On these systems Postgres (non-timescale) was used, running on the same server, so RAM and core numbers cover both NetXMS and DB engine.
Number of datapoints per second was obtained from the DB by this query: SELECT polling_interval, retention_time, count(polling_interval) FROM items GROUP BY polling_interval, retention_time ORDER BY retention_time, polling_interval;
| X | Y | Z |
| Objects | 20554 | 56040 | 41542 |
| Monitored nodes | 2175 | 2656 | 5376 |
| Collectible DCIs | 34260 | 185742 | 372240 |
| Collected datapoints per second | 372 | 979 | 2290 |
| Stored datapoints, millions | 8995 | 14978 | 44195 |
| RAM, GB | 24 | 74 | 160 |
| CPU cores | 8 | 10 | 20 |
| DB size, GB | 237 | 1500 | 1500 |
| Bytes per datapoint | 53 | 108 | 61 |
Thanks Filipp!
Very helpful as usual... :)
Fabrizio