Repository navigation
docs(benchmarks): guide to results and known limits - #480
Merged
NandhaKishorM merged 1 commit intoSep 25, 2026
Merged
Conversation
Owner
|
Thank you, this is a really useful page. I checked each limit and figure against BENCHMARKS.md, the README and research/, and they all match, including the note about the calibration columns that predate the clamp. It gives readers one place to judge a result before they rely on it, without adding any new claims. Merging. |
This was referenced Sep 25, 2026
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.
Summary
docs/ + benchmarks.md # how to choose, read and reproduce published results index.md # link the new guide from the docs home pageAdds the “Benchmarks and known limits” guide requested in #390. It points readers to the existing tables, scripts and raw results; distinguishes fine-tuned from base-checkpoint results and third-party Jev comparisons; and gives practical checks for language, option count, calibration, wording, long inputs and latency. The guide uses the repository's published evidence and introduces no new benchmark claim.
Evidence
uvx --from zensical==0.0.64 --with mkdocstrings-python==2.0.9 --with ruff==0.16.8 zensical build --strict --clean— passed, “No issues found”.python tests/test_doc_tables.py— 54 passed, 0 failed.ruff check laya/ --select=E9,F63,F7,F82,F401,F811 --line-length=120andpython -m compileall -q laya/ tests/— passed.git diff --cached --check— passed.Merge Danger
Door: two-way
Blast Radius: docs
Only the guide and its home-page link change. Benchmark refresh work remains tracked in #285.