[SERVER-72074] Investigate implications of low priority index builds Created: 13/Dec/22  Updated: 20/Jan/23  Resolved: 20/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Jordi Olivares Provencio
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-01-23
Participants:

 Description   

Once the work to finalize a ticketholder implementation is complete inĀ SERVER-72072 we should investigate the performance impact of low priority index builds and determine if the existing performance workloads are indicative of real life scenariosĀ 



 Comments   
Comment by Jordi Olivares Provencio [ 20/Jan/23 ]

I've created PERF-3746 in order to modify the workload to reflect better real life scenarios. The list of modifications includes:

  • Test for concurrent writes to the same collection being indexed.
  • Increase the number of tickets to 32 from 5
  • Modify the concurrent workload to consist of inserts, updates, and deletes instead of modifying only 256 documents by continuous insert/remove
Generated at Thu Feb 08 06:20:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.