[SERVER-69659] Test performance of restoring index cursors during TTL deletes Created: 13/Sep/22  Updated: 06/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Shin Yee Tan Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: storex-ranked
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-56274 TTL deletes are much slower on descen... Closed
related to SERVER-65528 Use range bounded cursors for restori... Closed
Assigned Teams:
Storage Execution
Sprint: 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
Participants:

 Description   

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.


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