Six questions to ask a published SGLang benchmark
Six questions in a column: version stated, workload matches yours, memory budgets matched, concurrency under the graph limit, flags mapped across engines, and who paid. A no on any question leads right to what the result can still tell you. Six yes answers lead to testing the mechanism on your own server.
1 · SGLang version stated?
no
an unknown build: anecdote only
2 · workload matches yours?
no
describes another workload
3 · memory budgets matched?
no
compares two KV pool sizes
4 · concurrency under graph limit?
no
measured eager decode
5 · flags mapped across engines?
no
a flag error can decide it
6 · who paid is stated?
no
read it as that party's claim
yes
test the mechanism on your server