Keep the AI cooking

Reports, experiments and numbers from a local AI lab.

QR code to donate to Keep the AI cooking QR CodeDonate to “Keep the AI Cooking”

Reports

Each report carries two machine-painted pictures: the number on the left is the robot's first impression, the picture on the right is how it imagines the story.

An image every 84 s on a used RX 580 — 5.2 Wh, no more blank frames

A width-32 clamp made every image pure white. Four kernel bugs later the same RX 580 renders 4.19× faster — measured, code included.

Don't optimise that kernel — 4× faster bought 1.4% of an image

One bank-conflict fix, two programs: a large prefill win where the matrix tile is the whole workload, and 1.4% per step with byte-identical images where it is a guest.

Output you can trust — six formats were returning wrong numbers

Six quantised formats returned wrong numbers on this GPU, so llama.cpp quietly routed them to the CPU. Now they agree with the reference on all 1347 shape tests — with q3_K still gated.

A coding task in half the time — 128 s → 66 s on a used RX 580

A tiled matrix multiply plus one float of padding took prompt processing from 91.7 to 295.7 t/s, and a re-encoded model file doubled generation — a real 128 s agent task now runs in 66 s.

Five chefs, one island — the 4B spent 29 minutes and served nothing

Ling baked the Three.js island in 5m42s at 19.5 t/s. LFM3 wrote a placeholder camera, Qwen forgot the clock, and both Sparks ran into a wall. Six files run on the page.