-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Execution Team 2022-10-17, Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-12-26, Execution Team 2023-05-01, Execution Team 2023-05-15
SERVER-56274 (TTL deletes are much slower on descending indexes than ascending indexes) was unknown until a user reported it. We address SERVER-56274 in SERVER-65528 by utilizing bounded cursors. It would be nice to add coverage to detect any future regressions as well as confirm the performance improvements of SERVER-65528 to ensure that TTL deletes now perform similarly on descending indexes as ascending indexes.
This can be done either with google benchmarks or a genny workload. If using benchmarks, it would be useful to have one for ascending ttl indexes and descending ttl indexes to compare the performance of both.
- related to
-
SERVER-56274 TTL deletes are much slower on descending indexes than ascending indexes
- Closed
-
SERVER-65528 Use range bounded cursors for restoring index cursors after yielding
- Closed