[SERVER-20572] Investigate snapshot thread performance for read committed queries on secondaries Created: 22/Sep/15  Updated: 06/Dec/22  Resolved: 15/Nov/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-20494 Enable reading from CSRS secondaries Closed
depends on SERVER-20161 Change snapshot thread notification t... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Running merge_chunks_test.js goes from 20 seconds to 2 minutes
after this commit when switching CSRS to use read pref nearest – SERVER-20494.



 Comments   
Comment by Eric Milkie [ 15/Nov/16 ]

Not going to do SERVER-20161

Comment by Eric Milkie [ 06/Oct/15 ]

This will need investigation if/when we reintroduce the cappedInsertNotifier changes.

Comment by Githook User [ 22/Sep/15 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-20572: revert snapshot thread using cappedInsertNotifier for performance evaluation (SERVER-20161)
Branch: master
https://github.com/mongodb/mongo/commit/9eeac28ad54382ddf3fa46dddbc704a36da7a5ac

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