[SERVER-79043] Create testing environment for readahead Created: 18/Jul/23  Updated: 24/Jul/23  Resolved: 24/Jul/23

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

Type: Task Priority: Major - P3
Reporter: Matt Kneiser Assignee: Huayu Ouyang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-79044 Run 1TB clone with WT readahead Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-07-24, Execution NAMR Team 2023-08-07
Participants:

 Description   

In order to hit a high water mark for fleshing out ideas in this spike, this ticket is to setup the testing environment that will work around current WT readahead issues.

Requirements

  • Some combination of bash scripts and/or jstests
  • Runs on one machine (m5.8xlarge)
  • 2 shards
    • each has its own dbpath linked to a dedicated gp3 volume w/250 MB/s throughput
    • donor => uses a mongod with readahead enabled
    • recipient => uses a mongod with readahead disabled

Testing against a much smaller subset of generated data would be a good idea to validate the testing procedure.


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