-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v5.0
-
Sharding 2021-07-12, Sharding 2021-07-26
-
2
This class is used to create a histogram, but it is specialized to only track information about reads, writes, commands, and transactions. The task for this ticket is to create a generalized version of this class that can track any operation type. Initially this will be used in the resharding project. The main requirement is to be able to export the histogram data to t2 via serverStatus, as is currently done by the OperationLatencyHistogram::append method.
- is depended on by
-
SERVER-57695 Measure latency/throughput of ReshardingOplogFetcher::consume aggregation query
- Closed
-
SERVER-57697 Measure latency/throughput of ReshardingOplogApplier::_applyBatch
- Closed
-
SERVER-57698 Measure latency/throughput of getNextBatch call in ReshardingOplogApplier
- Closed
-
SERVER-57700 Measure latency/throughput of resharding::data_copy::fillBatchForInsert in ReshardingCollectionCloner::doOneBatch
- Closed
-
SERVER-57746 Measure latency/throughput of inserting a batch in ReshardingCollectionCloner::doOneBatch
- Closed
-
SERVER-57747 Measure latency/throughput of ReshardingTxnCloner::_getNextRecord
- Closed
-
SERVER-57748 Measure latency/throughput of ReshardingTxnCloner::doOneRecord
- Closed
- related to
-
SERVER-61018 Create a generic histogram type
- Closed