Skip to content

(DOCSP-15543): Remove inaccurate advice for read-heavy apps #5209

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

Merged
merged 1 commit into from
Apr 19, 2021
Merged

(DOCSP-15543): Remove inaccurate advice for read-heavy apps #5209

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
3 changes: 0 additions & 3 deletions source/administration/analyzing-mongodb-performance.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,6 @@ If there are numerous concurrent application requests, the database may have
trouble keeping up with demand. If this is the case, then you will need to
increase the capacity of your deployment.

For read-heavy applications, increase the size of your :term:`replica set` and
distribute read operations to :term:`secondary` members.

For write-heavy applications, deploy :term:`sharding` and add one or more
:term:`shards <shard>` to a :term:`sharded cluster` to distribute load among
:binary:`~bin.mongod` instances.
Expand Down