Delivery latency per path and resources per node type for logos delivery runs - #411
Merged
Merged
Conversation
radiken
force-pushed
the
alan/logos-delivery-latency
branch
from
September 24, 2026 09:30
26db1fa to
93f547a
Compare
radiken
changed the base branch from
alan/logos-delivery-experiment
to
alan/logos-delivery-store
September 24, 2026 09:30
Waku logs a receive time rather than a delay, so the latency plotter had nothing to read for a waku run. Each path is now measured from when its message entered the network: a lightpush message when its service node handled the request, a relay message at its publish target. Writes one CSV per path in the plotter's shape and a CDF of all three. Reproduces the relay sanity run's numbers exactly (n 99,900, p50 9.8, p90 17.4, p99 39.8, max 729.5 ms). Negative delays are kept and counted, since clocks on different machines disagree by a few ms. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Scrapes have been written as <name>.csv since the suffix change, but the plotter built <metric>/<name> when picking files by name, found nothing and dropped the path. Tests only covered the old unsuffixed layout. Either layout now resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
One scrape per stateful set, each query limited to that role's pods, so the box plots put node type on the x axis: bandwidth, memory and CPU for every role, and mean archive insert time for the store nodes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A CDF shows the tail well but hides how the paths compare in the middle, so the latency check also draws one box per path on a log axis with outliers shown. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
radiken
force-pushed
the
alan/logos-delivery-store
branch
from
September 28, 2026 11:15
e9e31a4 to
2f21e23
Compare
radiken
force-pushed
the
alan/logos-delivery-latency
branch
from
September 28, 2026 11:15
93f547a to
9ea637c
Compare
radiken
marked this pull request as ready for review
September 28, 2026 12:20
AlbertoSoutullo
approved these changes
Sep 29, 2026
radiken
added a commit
that referenced
this pull request
Oct 1, 2026
…ery runs (#411) Adds a delivery latency check for relay, lightpush and filter to the waku analyzer, and a scrape that plots bandwidth, memory and CPU per node type.
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
2 participants
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 a delivery latency check for relay, lightpush and filter to the waku analyzer, and a scrape that plots bandwidth, memory and CPU per node type. Stacked on #417.
Related to #374