There are lots of factors that determine the system health of a server. The hardware capabilities - CPU, memory or disk - is an important one, but also the server load - number of devices (Nodes to be polled, updated, audited, synchronised), number of products (NMIS, OAE, opCharts, opHA - each running different processes), number of concurrent users.
...
Code Block |
---|
omkd_performance_logs => false |
MongoDB memory usage
MongoDB, in its default configuration, will use will use the larger of either 256 MB or ½ of (ram – 1 GB) for its cache size.
MongoDB cache size can be changed by adding the cacheSizeGB argument to the /etc/mongod.conf configuration file, as shown below.
Code Block |
---|
storage: dbPath: /var/lib/mongodb journal: enabled: true wiredTiger: engineConfig: cacheSizeGB: 1 |
Here is an interesting information regarding how MongoDB reserves memory for internal cache and WiredTiger, the underneath technology. Also some adjustment that can be done: https://dba.stackexchange.com/questions/148395/mongodb-using-too-much-memory
Server examples
Two servers are compared in this section.
...
Daemons graphs:
omk:
mongo:
Stressed system
Status | ||||||
---|---|---|---|---|---|---|
|
System information:
Name | Value |
---|---|
nmisd_max_workers | 50 |
nmisd_scheduler_cycle | 30 |
nmisd_worker_cycle | 10 |
nmisd_worker_max_cycles | 10 |
nmis9d is crashing with no error messages.
Some server info:
- CentOS 7
- 463 Nodes
- Poller server