DB of choice and sizing - feedback requested
-
Used the sizing spreadsheet - average row size - with 700 nodes, 20 DCI's per node = 14,000 DCI's, 300 sec polling (CPU per second but file Systems 1 per 15 minute - so averaged) - with a 365 day retention = 124GB. Not everything will have 365 day retention - but - taking my worst possible case.
Based on the following post - I do not appear to be pushing NetXMS so
https://www.netxms.org/forum/general-support/netxms-cpu-usage-high/msg24645/#msg24645I started with PostgreSQL and unless anyone suggests otherwise, I will go with PostgreSQL - on same server as NetXMS - with 150'ish GB of SAN based SSD storage, a couple of cores and a chunk of mem (plenty of both an a B200 M3).
Suggestions / Feedback welcome.
-
We have very good experience with PostgreSQL, that's definitely our recommendation. You may also try TimescaleDB - this is PostgreSQL extension optimized for time series data. We have added support for TimescaleDB recently and so far it shows significant performance improvement for large deployments.
Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login