Current state of diagnostic latches as the time of filing this ticket:
On v4.4:
- Latches are enabled by default
- All release binaries have latches enabled
- Our sys-perf variants run with latches enabled
- We only have dbtests and unittests as test coverage with latches disabled
On v5.0:
- Latches are enabled by default
- Our release binaries have latches enabled, except for Amazon Linux 2023 variants
- Sys-perf: all binaries have latches enabled. It doesn’t look like we run sys-perf against Amazon Linux 2023
- Along with dbtests/unittests, we do run our core integration tests, but maybe not all of our extensive passthroughs with latches disabled.
On v6.0:
- Same as v4.4. Latches are enabled by default, and our sys-perf tests run as such. Similar limited test coverage.
On v7.0:
- Latches are enabled by default
- All release binaries have latches disabled
- Sys-perf: runs with latches disabled
We have comprehensive correctness coverage with latches enabled and disabled
On the main branch (upcoming v8.0):
- Latches are disabled by default
- All release binaries have latches disabled
- Our sys-perf variants run with latches disabled
- We have comprehensive correctness coverage with latches enabled and disabled
The goal of this ticket is to enable latches by default on v5.0 and v6.0 as part of our correctness testing. We will let this burn in for some period of time and if all goes well, we should look to ship these versions with latches disabled in production so we can improve performance.
- is related to
-
SERVER-86876 Disable diagnostic latches for sys-perf variants on 7.0
- Closed
-
SERVER-82476 Disable diagnostics latches by default
- Closed