[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: This further amortizes the costs of bookkeeping work over the whole batch. |
| Comment by Githook User [ 09/May/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This allows a lot of expensive work that is done inside of a mutex to be done |
| Comment by Githook User [ 09/May/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 09/May/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This is called under a big global lock and is substantially faster on some |
| Comment by Githook User [ 09/May/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |