[SERVER-83353] Investigate faster BSON stream reading in magic restore Created: 16/Nov/23  Updated: 17/Nov/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Ali Mir Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

After we get performance results from SERVER-83352, we should investigate if we can make the BSON stream reading of additional oplog entries faster. The default behavior is serially threading the stream, constructing an oplog entry, and writing it into the oplog collection.

Some ideas include: can we split up reading the stream and writing the oplog entries into the oplog collection into multiple threads? Can we devise a smarter way of storing the additional oplog entries in S3 so we don't have to read the stream serially?


Generated at Thu Feb 08 06:51:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.