Skip to content

Align performance docs with committed benchmark results - #12

Closed
bIackr0se wants to merge 1 commit into
mizorewww:mainfrom
bIackr0se:fix/benchmark-doc-source
Closed

bIackr0se wants to merge 1 commit into
mizorewww:mainfrom
bIackr0se:fix/benchmark-doc-source

Conversation

@bIackr0se

@bIackr0se bIackr0se commented Sep 23, 2026 •

Copy link
Copy Markdown

Summary

Fixes #11. The README latency figures came from an older run than the committed 22 September FP16 results in BENCHMARKS.md. Both READMEs and the suggested launch copy now use the 22 September figures. The dated 19 September research notes keep their original figures, with links pinned to the benchmark commit that produced them.

A regression test compares the published figures with the committed benchmark JSON and checks the historical links.

Tests

  • uv run --python 3.12 --frozen --extra dev --extra demo --extra reference pytest -q: 151 passed
  • uv run --python 3.12 --frozen --extra dev --extra demo --extra reference ruff check .: passed
  • uv run --python 3.12 --frozen --extra dev --extra demo --extra reference ruff format --check .: passed
  • uv run --python 3.12 --frozen --extra dev --extra demo --extra reference python -m build: wheel and sdist built

@bIackr0se
bIackr0se marked this pull request as ready for review September 23, 2026 10:03
@mizorewww

Copy link
Copy Markdown
Owner

Thanks for the contribution and the supporting detail. The project is focusing on maintaining a native MLX port aligned with upstream Laya.

We are not merging this independent benchmark-documentation change in the current upstream-sync release. The distinction between historical and newer measurements remains acknowledged in #11.

Closing this thread under that maintenance policy.

@mizorewww mizorewww closed this Oct 2, 2026
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.

README and PERFORMANCE_RESEARCH cite the 2026-09-19 benchmark run; BENCHMARKS.md and committed results are from the 2026-09-22 re-run

2 participants