feat(observability): extend bandwidth buckets past 10 GbE saturation#319
Open
worstell wants to merge 1 commit into
Open
feat(observability): extend bandwidth buckets past 10 GbE saturation#319worstell wants to merge 1 commit into
worstell wants to merge 1 commit into
Conversation
The bandwidth histogram added in #318 topped out at 5000 MiB/s (~5.2 GB/s), so any serve from ~5 GiB/s through the cachew server NIC ceiling collapses into the +Inf bucket and we lose the signal where we most need it. Add 10000 and 15000 MiB/s buckets so cachew.git.snapshot_serve_bandwidth_mbps can distinguish 'saturating a 10 GbE workstation' from 'approaching the server NIC limit', with some headroom past the theoretical max to spot misattribution. Amp-Thread-ID: https://ampcode.com/threads/T-019e41af-0a15-718d-a9d8-e26df6071f9b Co-authored-by: Amp <amp@ampcode.com>
worstell
force-pushed
the
feat/bandwidth-buckets-100gbps
branch
from
4262774 to
b02141f
Compare
worstell
changed the title
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.
The bandwidth histogram added in #318 topped out at 5000 MiB/s (~5.2 GB/s), so any serve from ~5 GiB/s through the cachew server NIC ceiling (~12 GiB/s for 100 Gbps NICs) collapses into the
+Infbucket and we lose the signal where we most need it.Adds 10000 and 15000 MiB/s buckets so
cachew.git.snapshot_serve_bandwidth_mbpscan distinguish 'saturating a 10 GbE workstation' from 'approaching the server NIC limit', with some headroom past the theoretical max to spot misattribution.For context, the raw curl baseline we measured from a workstation was ~588 MiB/s — a small fraction of available server bandwidth, which is why visibility past the current top bucket matters for the next round of benchmarking.