bench(epp): add scorer comparison benchmark for issue #655 - #2222
Draft
pazqo wants to merge 1 commit into
Draft
Conversation
Demonstrate the value of token-aware scoring vs count-based scoring under heterogeneous workloads. The benchmark simulates scheduling 200 requests across 10 endpoints and reports load_cv (coefficient of variation of token load), showing that token-load-scorer achieves 140-700x better load balance than queue-scorer when request sizes vary. Signed-off-by: Stefano Pascolutti <spascolu@redhat.com>
github-actions
Bot
added
the
size/L
Contributor
|
🚨 Unsigned commits detected! Please sign your commits. For instructions on how to set up GPG/SSH signing and verify your commits, please see GitHub Documentation. |
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
1 participant
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.
Demonstrate the value of token-aware scoring vs count-based scoring under heterogeneous workloads. The benchmark simulates scheduling 200 requests across 10 endpoints and reports load_cv (coefficient of variation of token load), showing that token-load-scorer achieves 140-700x better load balance than queue-scorer when request sizes vary.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Release note (write
NONEif no user-facing change):