Skip to content

docs: mark benchmark metrics by implementation status - #46

Closed
KeuqS wants to merge 1 commit into
Continum-Computing:mainfrom
KeuqS:docs/44-metric-statuses
Closed

KeuqS wants to merge 1 commit into
Continum-Computing:mainfrom
KeuqS:docs/44-metric-statuses

Conversation

@KeuqS

@KeuqS KeuqS commented Oct 13, 2026

Copy link
Copy Markdown

Summary

  • Mark each README metric as Measured or Planned.
  • Rename the latency row to reflect the one full forward pass that the runner actually times.
  • Clarify that prefill/decode split, throughput, peak memory, and energy-per-token are not implemented.

Validation

  • Cross-checked the metric names and outputs with profiling/benchmark_runner.py.
  • Documentation-only change; no benchmark execution is required.

Closes #44

@Lincoln-developer Lincoln-developer left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you for submitting this pull request.

@Lincoln-developer Lincoln-developer left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

One note that is not a blocker. The branch is behind main, which has moved since you opened this. Updating the branch would re-run CI against current main and we merge this successfully.

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.

Mark each README metric as measured or planned

2 participants