Model benchmarks

Qwen-LowTemp local LLM performance

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

llama.cpp
ShareRedditX

Model size

1.5B

Peak speed

232.4 tok/s

Average speed

224.6 tok/s

Avg PP

6513.6 tok/s

Min memory

3.1 GB

Max context

32,768 tokens

Avg output / run

29,430 tokens

Avg runtime / run

2m 24s

Avg quality

24.7

Benchmark runs

10

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 10 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.924.730.0
Agent Workflow49.768.180.4
Code Generation2.25.59.5
Role Play & Narrative6.611.114.6
Research & Analysis0.514.026.5

Performance by hardware and tool

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

HardwareToolQuantBest tok/sAvg tok/sMemoryContextQualityRuns
Tesla V100-PCIE-32GBllama.cpp—232.4 tok/s224.6 tok/s3.1 GB32,768 tokens24.710

Benchmark runs

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

Frequently asked questions

Is Qwen-LowTemp good for agentic (tool-using) tasks?
In our benchmarks, Qwen-LowTemp scores 68.1/100 for agentic workflows. It runs at about 224.6 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-LowTemp for local inference?
Across 10 community benchmark runs, Qwen-LowTemp reaches up to 232.4 tok/s and averages 224.6 tok/s, with the fastest results on Tesla V100-PCIE-32GB.
How much memory does Qwen-LowTemp need?
The leanest observed configuration used about 3.1 GB of memory.
Which tools have been used to run Qwen-LowTemp?
Benchmarks were submitted using llama.cpp. Results are community-contributed and updated as new runs arrive.