This repository was archived by the owner on May 1, 2025. It is now read-only.
DOCSP-44657-mongosync-latency-performance #514
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
jmd-mongo
force-pushed
the
DOCSP-44657
branch
from
1ee825d to
8a69af8
Compare
jmd-mongo
force-pushed
the
DOCSP-44657
branch
from
8a69af8 to
73af4da
Compare
rohshar
suggested changes
Dec 9, 2024
rohshar
suggested changes
Dec 10, 2024
Comment on lines
384
to
385
| Mongosync writes operations and updates its own metadata on the | ||
| destination cluster in batches in a transaction. This can result in |
Collaborator
There was a problem hiding this comment.
Suggested change
| Mongosync writes operations and updates its own metadata on the | |
| destination cluster in batches in a transaction. This can result in | |
| Mongosync does operations and updates its own metadata in batches in a transaction on the | |
| destination cluster. This can result in |
Collaborator
Author
There was a problem hiding this comment.
Updated. Thanks!
| cross-shard transactions, which may be more costly if the shards are | ||
| far apart. | ||
|
|
||
| Latency between the nodes of each individual replica set on the source or destination |
Collaborator
There was a problem hiding this comment.
Suggested change
| Latency between the nodes of each individual replica set on the source or destination | |
| Latency between the nodes of any replica set (including shard backing replica set) on the source or destination cluster |
Collaborator
Author
There was a problem hiding this comment.
Updated, but added the parenthetical info to the body of the text to keep the title length manageable.
jmd-mongo
commented
Dec 10, 2024
Comment on lines
384
to
385
| Mongosync writes operations and updates its own metadata on the | ||
| destination cluster in batches in a transaction. This can result in |
Collaborator
Author
There was a problem hiding this comment.
Updated. Thanks!
| cross-shard transactions, which may be more costly if the shards are | ||
| far apart. | ||
|
|
||
| Latency between the nodes of each individual replica set on the source or destination |
Collaborator
Author
There was a problem hiding this comment.
Updated, but added the parenthetical info to the body of the text to keep the title length manageable.
rohshar
approved these changes
Dec 10, 2024
jmd-mongo
force-pushed
the
DOCSP-44657
branch
from
9882438 to
c08bcc7
Compare
sarah-olson-mongodb
approved these changes
Dec 10, 2024
Collaborator
sarah-olson-mongodb
left a comment
sarah-olson-mongodb
left a comment
There was a problem hiding this comment.
Thanks @jmd-mongo! LGTM
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIPTION
Documents
mongosynclatency performance considerations.JIRA
https://jira.mongodb.org/browse/DOCSP-44657
STAGING
Performance -- Network Latency