[SERVER-66574] Large discrepancy of performance results of change_streams_throughput between Linux 3-Node ReplSet and Linux 3-Node ReplSet (all feature flags) variants Created: 19/May/22 Updated: 27/Oct/23 Resolved: 26/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.1.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mindaugas Malinauskas | Assignee: | Denis Grebennicov |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Sprint: | QE 2022-05-30, QE 2022-06-13, QE 2022-06-27, QE 2022-08-08 |
| Participants: |
| Description |
|
There is a large discrepancy (>2x) of performance results of change_streams_throughput between Linux 3-Node ReplSet and Linux 3-Node ReplSet (all feature flags) variants. Performance result examples: Results from Linux 3-Node ReplSet (all feature flags): It shows that the performance results deteriorated no later than commit 2d9191c on May 18, 2021. Links to test results:
|
| Comments |
| Comment by Denis Grebennicov [ 26/Jul/22 ] |
|
This issue has already been investigated as part of this BF: https://jira.mongodb.org/browse/BF-21288 The issue arised from turning on writeConcern majority feature flag: https://jira.mongodb.org/browse/SERVER-53439 Since writeConcern majority caused a lot of performance data to drop, the performance team decided to have the feature flag off in regular performance tests and turned on in all feature flags runs, as described here: https://jira.mongodb.org/browse/PERF-2356 |