-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - Q3+ Backlog
-
None
WT-14542 has created a cursor statistic to measure the performance of cursor opens. The problem is that we want to test performance statistics under release mode but we also don't want the performance impact that comes from tracking these opens. We have a chicken and egg problem.
Currently it runs under only HAVE_DIAGNOSTIC, meaning we don't have meaningful performance metrics against customer workloads. The ticket is to investigate whether it gives any meaningful data under HAVE_DIAGNOSTIC mode if not, we should investigate on how we can measure the cursor performance under release. Maybe through adding a config to WiredTiger configuration and have cursor specific tests enabled on the MongoDB side
- is related to
-
WT-14542 Enable caching for layered cursors and their constituents in WT
-
- Closed
-