Matched Ollama and llama.cpp CPU Test
Four exact Q4_K_M GGUFs received the same raw prompt, context, thread count, batch settings, sampler, and 96-token output through Ollama 0.32.1 and native llama.cpp commit 9a286ac.
This page keeps the shared controls, retained measurements, failures, and comparison limits together. The linked files are there when you need the underlying table or method.
Comparison boundary
Internal generation rates are comparable inside this eight-row test. Model load time was not an identical part of the timed path.
Related pages
Useful comparisons from this test
Recorded results
Open the details under any row for the specific setup, outcome, artifact identity, and supporting file.
| Model and artifact | Runtime and mode | Generation | Prompt | Peak | State |
|---|---|---|---|---|---|
| Qwen3 0.6B Q4_K_M | llama.cpp 9a286ac CPU · Matched server request | 6.725 tok/s | 10.48 tok/s | 81 °C | Published result |
Open result detailsWhy this model is hereThe smallest matched X1S model completed both CPU runtimes and all three explicit llama.cpp device modes. It was small enough to show the CPU, mixed host-operation, and full-Vulkan differences without crossing into the larger-model i915 failures. What ranQ4_K_M ran through llama.cpp 9a286ac using CPU in Matched server request mode on Youyeetoo X1S. Three measured requests completed with a clean kernel window. Recorded setup
Artifact SHA-256 | |||||
| Qwen3 0.6B Q4_K_M | Ollama 0.32.1 CPU · Matched server request | 7.809 tok/s | 13.24 tok/s | 81 °C | Published result |
Open result detailsWhy this model is hereThe smallest matched X1S model completed both CPU runtimes and all three explicit llama.cpp device modes. It was small enough to show the CPU, mixed host-operation, and full-Vulkan differences without crossing into the larger-model i915 failures. What ranQ4_K_M ran through Ollama 0.32.1 using CPU in Matched server request mode on Youyeetoo X1S. Ollama reported 16.11% higher internal generation throughput than the paired llama.cpp row. Recorded setup
Artifact SHA-256 | |||||
| Qwen3 1.7B Q4_K_M | llama.cpp 9a286ac CPU · Matched server request | 2.852 tok/s | 3.849 tok/s | 83 °C | Published result |
Open result detailsWhy this model is hereThis model completed the matched CPU comparison and the full CPU, mixed, and Vulkan mode test. The original X1S work put it in the usable interactive tier, so it became the second clean model for checking whether the Vulkan pattern held beyond 0.6B. What ranQ4_K_M ran through llama.cpp 9a286ac using CPU in Matched server request mode on Youyeetoo X1S. Three measured requests completed with a clean kernel window. Recorded setup
Artifact SHA-256 | |||||
| Qwen3 1.7B Q4_K_M | Ollama 0.32.1 CPU · Matched server request | 3.321 tok/s | 5.075 tok/s | 83 °C | Published result |
Open result detailsWhy this model is hereThis model completed the matched CPU comparison and the full CPU, mixed, and Vulkan mode test. The original X1S work put it in the usable interactive tier, so it became the second clean model for checking whether the Vulkan pattern held beyond 0.6B. What ranQ4_K_M ran through Ollama 0.32.1 using CPU in Matched server request mode on Youyeetoo X1S. Ollama reported 16.46% higher internal generation throughput than the paired llama.cpp row. Recorded setup
Artifact SHA-256 | |||||
| Qwen3 4B Instruct Q4_K_M | llama.cpp 9a286ac CPU · Matched server request | 1.484 tok/s | 1.899 tok/s | 81 °C | Published result |
Open result detailsWhy this model is hereThe Q4_K_M file completed the matched CPU test, then reached an i915 reset timeout during full Vulkan. It marks the point where the clean small-model Vulkan result stopped scaling into a reliable larger-model run on this software stack. What ranQ4_K_M ran through llama.cpp 9a286ac using CPU in Matched server request mode on Youyeetoo X1S. Three measured requests completed with a clean kernel window. Recorded setup
Artifact SHA-256 | |||||
| Qwen3 4B Instruct Q4_K_M | Ollama 0.32.1 CPU · Matched server request | 2.002 tok/s | 2.789 tok/s | 81 °C | Published result |
Open result detailsWhy this model is hereThe Q4_K_M file completed the matched CPU test, then reached an i915 reset timeout during full Vulkan. It marks the point where the clean small-model Vulkan result stopped scaling into a reliable larger-model run on this software stack. What ranQ4_K_M ran through Ollama 0.32.1 using CPU in Matched server request mode on Youyeetoo X1S. Ollama reported 34.89% higher internal generation throughput than the paired llama.cpp row. Recorded setup
Artifact SHA-256 | |||||
| Phi-4 Mini Q4_K_M | llama.cpp 9a286ac CPU · Matched server request | 1.57 tok/s | 2.115 tok/s | 82 °C | Published result |
Open result detailsWhy this model is herePhi-4 Mini completed both matched CPU servers. Its full-Vulkan window coincided with an i915 GPU hang. It provides a second model family inside the matched runtime result and a retained failure outside the clean Vulkan pair. What ranQ4_K_M ran through llama.cpp 9a286ac using CPU in Matched server request mode on Youyeetoo X1S. Three measured requests completed with a clean kernel window. Recorded setup
Artifact SHA-256 | |||||
| Phi-4 Mini Q4_K_M | Ollama 0.32.1 CPU · Matched server request | 2.072 tok/s | 3.131 tok/s | 82 °C | Published result |
Open result detailsWhy this model is herePhi-4 Mini completed both matched CPU servers. Its full-Vulkan window coincided with an i915 GPU hang. It provides a second model family inside the matched runtime result and a retained failure outside the clean Vulkan pair. What ranQ4_K_M ran through Ollama 0.32.1 using CPU in Matched server request mode on Youyeetoo X1S. Ollama reported 32.00% higher internal generation throughput than the paired llama.cpp row. Recorded setup
Artifact SHA-256 | |||||
Supporting evidence
Results and method
These are the few files that support this page directly. The repository holds the wider project history.
Controls
- Same raw prompt and exact content-addressed GGUF
- 4,096-token context
- Four threads
- Batch and microbatch 512
- Temperature 0, seed 42, top-k 1
- One warmup and three measured requests per model
- Exactly 96 generated tokens
What this run established
- $All 24 measured requests completed with clean kernel windows.
- $Ollama reported 16.1% to 34.9% higher internal generation throughput in this configuration.
- $The two runtimes produced different greedy text, which was retained as part of the record.