[SERVER-79505] Investigate effects of tuning remaining throughputProbing parameters Created: 31/Jul/23  Updated: 29/Oct/23  Resolved: 14/Aug/23

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

Type: Task Priority: Major - P3
Reporter: Shin Yee Tan Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-77821 Simulator for ticket holder monitor Closed
Related
is related to SERVER-78319 Investigate execution control tuning ... Closed
Assigned Teams:
Storage Execution NAMER
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-08-21
Participants:

 Description   

InĀ SERVER-78319 we investigate how throughputProbingReadWriteRatio impacts the performance of the system with different workloads. With the convergence tests simulator, we want run investigate the performance of running desired workloads with tuning the remaining parameters:

  • throughputProbingInitialConcurrency
  • throughputProbingMinConcurrency
  • throughputProbingMaxConcurrency
  • throughputProbingConcurrencyMovingAverageWeight
  • throughputProbingStepMultiple


 Comments   
Comment by Githook User [ 14/Aug/23 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-79505 Respect server parameter values for throughput probing simulation
Branch: master
https://github.com/mongodb/mongo/commit/2377347b2accc43d0e5d8527c271e8200d5fd4b3

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