Model benchmarks

Qwen-HighTemp local LLM performance

As of November 2026, Qwen-HighTemp runs at up to 237.2 tok/s for local inference (best of 9 community benchmark runs across 1 GPU).

llama.cpp
ShareRedditX

Model size

1.5B

Peak speed

237.2 tok/s

Average speed

234.5 tok/s

Avg PP

7725.1 tok/s

Min memory

3.1 GB

Max context

32,768 tokens

Avg output / run

7,107 tokens

Avg runtime / run

33s

Avg quality

25.6

Benchmark runs

9

GPUs tested

1

Quality by task

Average LLM-judged quality (0–100) with the run-to-run spread shown as a P5–P95 band, overall and for each benchmark task, across all 9 runs. The low and high columns show how much the judge’s score varies between runs, and need at least two runs to display.

TaskP5 (low)AvgP95 (high)
Overall17.825.637.0
Agent Workflow18.542.270.3
Code Generation6.09.312.1
Role Play & Narrative13.728.245.3
Research & Analysis12.922.636.0

Performance by hardware and tool

Every hardware/tool/quantization combination Qwen-HighTemp has been benchmarked on, ranked by peak token generation speed. Last updated November 2026.

HardwareToolQuantBest tok/sAvg tok/sMemoryContextQualityRuns
Tesla V100-PCIE-32GBllama.cpp—237.2 tok/s234.5 tok/s3.1 GB32,768 tokens25.69

Benchmark runs

All 9 Qwen-HighTemp runs submitted so far — expand one for its hardware, quality breakdown and per-scenario detail.

Frequently asked questions

Is Qwen-HighTemp good for agentic (tool-using) tasks?
In our benchmarks, Qwen-HighTemp scores 42.2/100 for agentic workflows. It runs at about 234.5 tok/s, so if you want more speed, unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_M is faster (~303.4 tok/s) and still scores well for agentic workflows (82.6/100).
How fast is Qwen-HighTemp for local inference?
Across 9 community benchmark runs, Qwen-HighTemp reaches up to 237.2 tok/s and averages 234.5 tok/s, with the fastest results on Tesla V100-PCIE-32GB.
How much memory does Qwen-HighTemp need?
The leanest observed configuration used about 3.1 GB of memory.
Which tools have been used to run Qwen-HighTemp?
Benchmarks were submitted using llama.cpp. Results are community-contributed and updated as new runs arrive.