fix wormhole bench: extend histogram buckets to 30min - #1404
Merged
Conversation
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
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.
Summary
wormhole_vaa_latency_millisecondsbuckets from 600_000ms cap to 1_800_000ms (30min)Why
Ethereum and Arbitrum VAAs only sign after L1 Casper FFG finality (~12.8min ideal, up to ~19min real). With the previous 600_000ms bucket ceiling,
histogram_quantilepinned Eth/Arb p50/p90/p99 all to 600s (the bucket edge), which is not the real latency.Prior sample distribution: Ethereum 208/219 samples in +Inf, Arbitrum 5/5 in +Inf.
Deploy
docker build --no-cache, thendocker compose up -d --force-recreate wormhole-vaa-latencyTest plan