[SERVER-20779] Oplog performance on primary does not scale Created: 06/Oct/15  Updated: 24/Aug/16  Resolved: 24/Aug/16

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

Type: Bug Priority: Major - P3
Reporter: Martin Bligh Assignee: Backlog - Tuning Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-15091 Reduce replication lag when primary i... Closed
Operating System: ALL
Participants:

 Description   

32 threads insert, 24 CPU box.
standalone: 1.15M insert/s
with oplog: 186K insert/s
Believed to be single threading in logOp from OplogHack mutex.
Contention from delete holding mutex whilst walking DLL is linear with list size.
Proposed fix of O(1) delete by retaining pointer handle to reference back


Generated at Thu Feb 08 03:55:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.