-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-10-30
According to the flame graph, about 4% of the bulkWrite operation's time is spent in populating the cursor response on mongod (when a bulkWrite with 1000 insert operations is run). When I eliminated this method (by returning an empty cursor response instead here) I saw the corresponding improvement.
Consider ways to optimize this method. And if possible, consider omitting success responses from the response and use a counter n instead, as the existing insert codepath does.
See SERVER-76662 for flame graphs.
- is related to
-
SERVER-76662 bulkWrite perf testing against vectorized inserts
- Closed
-
SERVER-82054 Investigate and fix slow bulkWrite request parsing on mongod
- Closed
- related to
-
SERVER-82056 Investigate and fix slow bulkWrite addition of insert replies.
- Closed