Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Storage Execution
-
1
Description
During the investigation of a performance regression BF-29842, I find that the classic engine uses WriedTigerIndexCursorBase::curr which consumes 0.5% CPU, but the new SBE engine uses WriedTigerIndexCursorBase::getKeyStringEntry which consumes 5.75% CPU.
The profiler shows a large amount of CPU on memory allocation in KeyString copy, but not for curr(). The curr() version avoids returning full BSON object in some cases, we should do some optimization on the keyString version.
Attachments
Issue Links
- depends on
-
SERVER-86151 Create unowned key_string::View type
-
- Open
-
- related to
-
SERVER-65089 Avoid unnecessary KeyString copies in index interface
-
- Open
-