[DOCS-11705] Suggestion for MongoDB Production Note for VMware. Created: 15/May/18 Updated: 30/Oct/23 Resolved: 15/May/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Tom Li | Assignee: | Andrew Aldridge |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 39 weeks, 2 days ago |
| Story Points: | 0.1 |
| Description |
|
In our current MongoDB document Production Notes, under the VMware section, the following CPU reservation recommendation has been given to the customer:
I am not aware of the historical reason why this is given to the customer, but VMware CPU reservation does not work like this. When setting up CPU reservation for a VM, you can not reserve number of vCPUs, but the CPU cycles (MHz). It is then the hypervisor's job to guaranty the reserved CPU cycles are available to the VM even if the ESXi host is under CPU resource contention. I suggest removing the above recommendation from our Production Notes. |
| Comments |
| Comment by Githook User [ 15/May/18 ] |
|
Author: {'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}Message: |
| Comment by Githook User [ 15/May/18 ] |
|
Author: {'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}Message: |
| Comment by Githook User [ 15/May/18 ] |
|
Author: {'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}Message: |