[SERVER-75038] Throughput probing sets initial concurrency level even when feature flag is not enabled Created: 20/Mar/23 Updated: 29/Oct/23 Resolved: 22/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2023-04-03 | ||||
| Participants: | |||||
| Linked BF Score: | 105 | ||||
| Description |
|
The throughput probing algorithm sets the starting concurrency level regardless of whether the feature flag is enabled, but the algorithm only runs when the feature flag is enabled. So when the feature flag isn't enabled we end up just leaving it to the (lower) starting value. |
| Comments |
| Comment by Githook User [ 21/Mar/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |