Skip to content

DOCS-4037: adds vmware considerations to production notes #2229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

DOCS-4037: adds vmware considerations to production notes #2229

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions source/administration/production-notes.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -524,9 +524,18 @@ should set ``tcp_keepalive_time`` to 120 to ameliorate this problem.
VMWare
``````

MongoDB is compatible with VMWare. As some users have
run into issues with VMWare's memory overcommit feature,
disabling the feature is recommended.
MongoDB is compatible with VMWare.

As some users have run into issues with VMWare's memory overcommit
feature, you should disable the feature.

Further, MongoDB is known to run poorly with VMWare's balloon driver
(``vmmemctl``), so you should disable this as well. VMWare uses the
balloon driver to reduce physical memory usage on the host hardware by
allowing the hypervisor to swap to disk while hiding this fact from
the guest, which continues to see the same amount of (virtual)
physical memory. This interferes with MongoDB's memory management,
and you are likely to experience significant performance degradation.

It is possible to clone a virtual machine running MongoDB.
You might use this function to
Expand Down