v0.4.11

A fused session holds a fifth of the host memory it held yesterday.

The 1.2 GiB it carried was one pinned allocation, made to read the three integers the grid barrier writes, and not the compile it was blamed on. The first pinned allocation in a process costs that whatever its size. Reading the same words with an ordinary device to host copy takes SmolLM2 135M on a 4090 from 1468 MiB to 279 and Qwen 2.5 0.5B from 1481 to 550, both under llama.cpp on the same file in the same sitting, with decode and card figures unmoved.

The gpc section of docs/validation/bench.md was retaken on this build, rivals included, five runs each at a 514 token prompt and 128 generated.

model	molla host	llama.cpp host	molla decode	llama.cpp decode
SmolLM2 135M q8_0	279	444	490.4	894.3
Qwen 2.5 0.5B q4_K_M	550	807	383.2	752.0
Llama 3.1 8B q4_K_M	1044	5027	95.5	163.3

Source only, for the licensing reason in the changelog. Build with pixi run build.

What's Changed

• Cover the empty fused plan by @tamnd in #224
• Read the barrier words back without a pinned host buffer by @tamnd in #225
• Release 0.4.11 by @tamnd in #226

Full Changelog: v0.4.10...v0.4.11