tools: add one-command datapoint runner - #952
Open
gouravkargwal wants to merge 1 commit into
Open
Conversation
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.
Adds
c/tools/datapoint.py— a stdlib-only, one-command runner for the standard machine datapoint that docs/benchmarks.md asks for (engine load, capped greedy decode tok/s, iobench disk figures), printing a ready-to-paste markdown block.What it measures, and how:
--max-newtokens, so the token count is known without re-tokenizing output. TEMP=0 greedy.purgeif permitted, otherwise a portable temp-file write larger than RAM). iobench cold runs right after eviction, before decode re-warms the container.--no-evictskips it.docs/benchmarks.md Quick Start now points at it as step 3 (steps renumbered).
The M3 datapoint row it produced is in a separate PR (docs: add Apple M3 16 GB OLMoE datapoint row, #951).