Add latency offload panels to enterprise dashboard#39
Open
briiians wants to merge 1 commit into
Open
Conversation
… percent of average time saved, and Hit vs Miss Latency showing average time differences for diff object types
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two new panels to the Latency section of the Varnish Enterprise
metrics dashboard to show time saved.
Traffic offload (latency) - stat tile
Shows what percentage of the total latency is absorbed by Varnish. The formula compares actual total response time against the cost if every request had been a cache miss, and is based similarily to the Traffic Offload (bytes) tile above.
Hit vs Miss Latency - timeseries
Shows average response time for cache hits vs misses over time, split
into typical/normal (50 percentile) and large object (90th percentile) lines. The
gap between the green hit lines and orange miss lines is the per-request
time saved. The idea/assumption here is to look at the percentile, 50 vs 90, as bell curve averages in delivery times, where we can assume the 90th percentile times are slower due to being a larger object or some other factor. Showing that more time is saved on different object types is important but breaking it down into each object type or buckets on object size could get quite messy on a graph. If someone has a different oppinion please let me know!