Repository navigation
Derive run throughput sparkline from bytes written - #33
Merged
Merged
Conversation
The sparkline plotted the controller's 5s snapshot of the agents' instantaneous MB/s, summed over VMs still working. On short runs a VM writes its few GiB between two snapshots and reports done before the next, so the series was mostly 0 and "peak 0" sat next to a real avgMBps. Derive the rate from the cumulative bytesWritten each sample already stores (averaged over >=10s to avoid agent/poll aliasing), keep the snapshot where it is higher, and show only the peak for finished runs instead of an always-zero "latest". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
Small runs (e.g. a 2-VM incremental) showed a flat sparkline and
peak 0right next to a realavgMBps. The series was the controller's 5 s snapshot of the agents' instantaneous fio rate, summed over VMs stillworking. A VM writes its few GiB between two snapshots and reportsdonebefore the next, so almost every sample is 0. The label also showed the latest sample, which is always 0 for a finished run.Fix (UI only)
web/src/throughput.ts: derive MB/s (MiB, same asavgMBps) from the cumulativebytesWritteneach sample already stores, averaged over ≥10 s so the 5 s agent report and the 5 s controller poll don't alias. Where the stored snapshot is higher (a real burst), use it instead. Existing runs benefit too, because no schema or backend change is needed.Sparkline.vue: finished runs showpeak N MB/s; running runs still show current rate · peak.Testing
npm run build(vue-tsc + vite) passes.0 … 0 363 0 …, new series0 … 123 363 481 461 218 3.🤖 Generated with Claude Code