[SERVER-43113] Check if a cached cursor exists before constructing configuration string in WiredTigerCursor Created: 30/Aug/19  Updated: 29/Oct/23  Resolved: 25/Jun/20

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Yuhong Zhang
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-06-29
Participants:
Linked BF Score: 0

 Description   

When creating WiredTigerCursors, we construct the entire configuration string and pass that to WiredTigerSessionCache::getCachedCursor. The majority of normal cursors utilize the session cache, and the implementation of getCachedCursor doesn't use the configuration string if a cached cursor is found.

Since cursor creation is in a hot path, we should first check the cache if a cursor is found, and only construct the configuration string for a new cursor when one isn't already open.



 Comments   
Comment by Githook User [ 25/Jun/20 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}

Message: SERVER-43113 Check if a cached cursor exists before constructing configuration string in WiredTigerCursor
Branch: master
https://github.com/mongodb/mongo/commit/b2869d11c9e3075f7224bbbdbd1218fe3715f07a

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