Repository navigation
bench: community report — RTX 5090, IQ3_S at 1M context (YaRN), agent-style workload (re-submission of #466) - #1134
Closed
gravitomagnetic wants to merge 1 commit into
Closed
gravitomagnetic wants to merge 1 commit into
gravitomagnetic wants to merge 1 commit into
Conversation
…t (YaRN), agent-style workload Re-submission of Niko1221#466 onto the cleaned history (that PR was auto-closed by the force-push, not rejected). Adds the 0.1.39 re-probe (regression closed, beats the 0.1.31 baseline at 32K/128K) and the preemption A/B (FIFO vs --batch 2: 5.3x/6.5x interactive-latency win, with the 32 GB VRAM budget finding and the batched-timings observability note). Raw JSON included.
Owner
|
Thank you. This folder is already in 0.1.40.2 from the original PR (authorship kept), so this re-file is a duplicate and is closed. |
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.
Re-submitting #466 onto the cleaned history — that PR was auto-closed by the force-push per @Niko1221's note, and its branch was built on the old history so it could not be reopened. This branch starts from the new
mainand carries the same content plus everything that lived in the closed PR's comments, folded into the README:tools/needle_bench.py).--batch 29.2 s / 4.8 s — 5.3× / 6.5×, with BYIELD interleaving visible in the serve log and the cost to A quantified (−2% prefill, −13% decode, +2 s wall).--batch 4OOMs at load;--batch 2needs--expert-cache 6500 --vram-reserve-mib 995(at 7500/700 it loads but dies on the first request needing slot 2). Suggested as a line in BATCHING.md.prompt_n: 0/ null client-side timings while the serve log has segment truth.No code changes — data + docs only, same as the original. Thanks for the porting offer in the closing note, but a clean re-PR is simpler now that we have the updated content.