Skip to content
This repository has been archived by the owner on Jul 16, 2021. It is now read-only.

Add latency metrics to ApplyRevisions in Sequencer #1252

Merged
merged 1 commit into from
Mar 28, 2019

Conversation

therealdrake
Copy link
Contributor

-Add an additional histogram metric to measure latency of ApplyRevision function
--Overall ApplyRevisionLatency
--ReadBatch
--GetAndVerifyMapLeavesByRevision
--SetLeavesAtRevision

-Add an additional histogram metric to measure latency of ApplyRevision function
--Overall ApplyRevisionLatency
--ReadBatch
--GetAndVerifyMapLeavesByRevision
--SetLeavesAtRevision
@codecov
Copy link

codecov bot commented Mar 28, 2019

Codecov Report

Merging #1252 into master will increase coverage by 0.15%.
The diff coverage is 81.81%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1252      +/-   ##
==========================================
+ Coverage   32.07%   32.23%   +0.15%     
==========================================
  Files          45       45              
  Lines        3482     3493      +11     
==========================================
+ Hits         1117     1126       +9     
- Misses       2180     2182       +2     
  Partials      185      185
Impacted Files Coverage Δ
core/sequencer/server.go 46.32% <81.81%> (+1.49%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 471988f...222a2c2. Read the comment docs.

@therealdrake therealdrake merged commit c68c235 into master Mar 28, 2019
@gdbelvin gdbelvin deleted the therealdrake-patch-1 branch March 28, 2019 22:44
gdbelvin added a commit that referenced this pull request Mar 29, 2019
* master:
  Remove trailing whitespace in sequencer_api.proto (#1253)
  Add latency metrics to ApplyRevisions in Sequencer (#1252)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants