Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gui: moving window average and max for tile primary metrics #3166

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

yufeng-jump
Copy link
Contributor

@yufeng-jump yufeng-jump commented Oct 18, 2024

Currently live values are computed from the end of the prior leader slot. Change to a 1-second moving average. Also change queries for our slots to return max within slot, so this would tell us for example the peak number of QUIC connections or peak fullness of the pack buffer that we observed within a slot.

@@ -17,7 +17,6 @@ runs:
run: |
set -x
sudo src/util/shmem/fd_shmem_cfg fini || true
sudo src/util/shmem/fd_shmem_cfg reset || true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move all the CI changes out to another PR if they are still needed?

@@ -586,21 +586,21 @@ potential underflow.
| Field | Type | Description
|---------------------|---------------------|------------
| next_leader_slot | `number\|null` | The next leader slot |
| tile_primary_metric | `TilePrimaryMetric` | Per-tile-type primary metrics. Some of these are point-in-time values (P), and some are aggregated since the end of the previous leader slot (A) |
| tile_primary_metric | `TilePrimaryMetric` | Per-tile-type primary metrics. Some of these are point-in-time values (P), and some are moving window averages (W) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mention that it's 1s moving average

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also is there a separate part of the docs clarifying that it's the max when querying a historical slot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants