[SERVER-56634] Performance workloads for server startup Created: 04/May/21  Updated: 25/Jul/23  Resolved: 25/Jul/23

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-62618 Avoid quadratic behavior at startup w... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

We often don't know that server startup is slow with a large number of collections until a customer observes a problem. It is a pretty common workflow for backup use cases and upgrade/downgrade.

We should consider adding performance workloads for the following common operations with a large number of collections (at least 1000):

  • Starting a replica set node after a clean shutdown
  • Starting a replica set node after an unclean shutdown
  • Starting a replica set node in standalone mode, and starting a standalone node in replica set mode
    • Both of these steps are required for backup procedures.
  • Upgrading a replica set node from the last stable version to the current version
  • Consider further separating tests into some that write to a subset of collections vs. all of them

Generated at Thu Feb 08 05:39:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.