[SERVER-24005] Improve primary write-side performance Created: 02/May/16  Updated: 19/Nov/16  Resolved: 17/May/16

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

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Integrate+Tuning 14 (05/13/16)
Participants:

 Description   

Currently enabling replication has a significant overhead on the primary in some workloads. We want a primary's performance to be as close to a standalone node's as possible.



 Comments   
Comment by Nick Judson [ 21/Jun/16 ]

I did a quick test yesterday and I didn't see this behavior with the latest 3.2 branch release. Thx.

Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-24005 Pass batches of DocWriters all the way down to the RecordStore

This further amortizes the costs of bookkeeping work over the whole batch.
Branch: master
https://github.com/mongodb/mongo/commit/839a4d88a9b4627f0aa69ad6faba2c36e10b41ae

Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-24005 Allow getNextOpTime() to hand out batches of OpTimes

This allows a lot of expensive work that is done inside of a mutex to be done
once per batch rather than once per document.
Branch: master
https://github.com/mongodb/mongo/commit/955304d50df6c94bb10e757736e531ce91627d23

Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-24005 inline WiredTigerRecoveryUnit::get()
Branch: master
https://github.com/mongodb/mongo/commit/0257f34483b0dee3691b8bd4a6715ac33c250b67

Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-24005 Use FastClockSource in getNextGlobalTimestamp()

This is called under a big global lock and is substantially faster on some
systems.
Branch: master
https://github.com/mongodb/mongo/commit/423ba14c79ab2749e8717cc36e4efdb204de9751

Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-24005 Mark WiredTigerRecordStore final
Branch: master
https://github.com/mongodb/mongo/commit/6cb108ba117f272f5a6db9cd99d4a5c30cc27d28

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