Skip to content

Stop ranking queues on payload size; publish CPU instead - #31

Merged
leo-gan merged 4 commits into
masterfrom
refactor-queue-metrics
Sep 1, 2026
Merged

Stop ranking queues on payload size; publish CPU instead#31
leo-gan merged 4 commits into
masterfrom
refactor-queue-metrics

Conversation

@leo-gan

@leo-gan leo-gan commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Summary

Validation

  • Tests: analysis 96, python 14, javascript 3, dashboard 22
  • Benchmarks: full, langs c csharp javascript python rust, stems 2026-09-01-144022 / 143923 / 144029 / 143936 / 144004
  • Experiments: timed 52 runs for those languages
  • Error CSVs: clean (0 rows)
  • Analysis: this-repo uv run analyze-benchmarks (210/310/270/160/140 groups)
  • Dashboard: sync-data.py → new *_latest.json.gz without median_size_bytes

Notes

  • Self-authored; GitHub cannot self-approve.

Size is a leftover serializer score. Every library in a cell moves the
same already-built payload, so “most compact” and speed-vs-size Pareto
were a horizontal line. Keep Size on the CSV as fixture metadata, treat
fidelity as a validity gate, and rank on handoff plus messages per
CPU-second (spin vs block). Dashboard, analysis, and experiment tables
follow that contract.
Write the terminology rule into improve-docs STYLE.md: the catalog
payload is a data type, not a fixture. Rename dashboard and analysis
identifiers to match. Remove Size, SizeGzip, SizeZstd, and
median_size_bytes from new CSV writes, stats, and experiment tables.
Old logs may still contain Size; analysis ignores it.
Re-ran full benches for C, C#, JavaScript, Python, and Rust with the
new CSV header (no Size/gzip/zstd). Analysis now emits msgs_per_cpu_sec
and no median_size_bytes. Experiment summaries keep write/read/handoff
only.
@leo-gan
leo-gan force-pushed the refactor-queue-metrics branch from d070fa5 to d87047c Compare September 1, 2026 21:43
@leo-gan
leo-gan merged commit b3a58e6 into master Sep 1, 2026
7 checks passed
@leo-gan
leo-gan deleted the refactor-queue-metrics branch September 1, 2026 21:44
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.

1 participant