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.
Getting (on MMLU-Redux-2, vs MMLU-Redux reported in the Qwen3 report)
vllm "model_name=Qwen/Qwen3-0.6B-Base,data_parallel_size=2,max_num_batched_tokens=100000,generation_parameters={temperature:0.6,top_p:0.95,top_k:20,min_p:0,presence_penalty:1,max_new_tokens:38912}" "lighteval|mmlu_redux_2|5|0"
(same as above with
"model_name=google/gemma-3-1b-pt,data_parallel_size=2,max_num_batched_tokens=2001,generation_parameters={temperature:0.6,top_p:0.95,top_k:20,min_p:0,presence_penalty:1,max_new_tokens:5},gpu_memory_utilization=0.8"
)It's impossible to know if the implem is exactly the same so we're imo within range (for ex, unsure if the report uses a logprob or generative approach - they use 5 shots which are likely not the same as ours and we know it can lead to up to 3 points diff, etc)
Not adding tests atm as we'll want to do all evals at the same time I think, with a setup running faster than our current one