[DOCS-13021] [OM] Memory requirements unclearly omit the backing mongods Created: 06/Sep/19 Updated: 29/Oct/23 Resolved: 03/Oct/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Kurowski | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
|||||||||||||||
| Participants: | ||||||||||||||||
| Days since reply: | 4 years, 18 weeks, 6 days ago | |||||||||||||||
| Story Points: | 2 |
| Description |
DescriptionA customer cited the OM hardware requirements page which states 15 GB RAM for the OM application plus 15 GB for a co-hosted backup daemon, however the actual memory use for their OM application was ~40 GB plus ~13 GB for the backing mongod servers, plus ~17 GB for the backup daemon mongod:
Customer requests this documentation be updated to more accurately estimate Ops Manager application server memory use expectations. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 03/Oct/19 ] | ||||||
|
Author: {'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Tony Sansone'}Message: (DOCSP-13080): Backport | ||||||
| Comment by Githook User [ 03/Oct/19 ] | ||||||
|
Author: {'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Tony Sansone'}Message: (DOCSP-13081): Backport | ||||||
| Comment by Githook User [ 03/Oct/19 ] | ||||||
|
Author: {'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Tony Sansone'}Message: ( | ||||||
| Comment by Scott Kurowski [ 30/Sep/19 ] | ||||||
|
I think prepending "resident" on OM memory use references would do more to make this issue go away for customers. | ||||||
| Comment by Anthony Sansone (Inactive) [ 12/Sep/19 ] | ||||||
|
scott.kurowski: The output of the top command may have been misinterpreted. Reviewing this output:
We want to examine the RES value: physical memory. (See the top man page.) Across all five processes, this adds up to 34.7 GB of physical memory, which is well within the stated hardware requirements (assuming < 2,000 hosts and 2 TB of blockstore storage):
The top command shows that these five processes are consuming a total of 13.9% of available physical memory. The host in question has more than 250 GB of physical memory available. The other value, VIRT, includes "the total amount of virtual memory used by the task. It includes all code, data and shared libraries plus pages that have been swapped out and pages that have been mapped but not used." (Emphasis mine.) This is the total amount of virtual memory that has been used recently and may be used in the near future. I don't believe the requirements need updating as these values appear within the recommended values. Barring any further clarification, I will close this ticket at the end of business on Thursday. I hope this helps! mihai.bojin, please correct me if I have misunderstood this information or the requirements as documented need additional clarification. |