News

Strata releases on our fleet: the agent updates, measures and optimizes

Our agent detects new Strata releases by coldniko, updates the machines and re-runs the benchmarks: decode up to 2.4× faster at 16K on a Tesla P100 system, +46% expert slots on a Radeon system, the Mac Studio confirmed optimal, and DeepSeek V4.1-Flash running locally.

Strata is a local AI inference engine developed by coldniko. Since mid-October we have been following its releases on several of our own machines. Every computer runs the same model, Qwen3.8-Flash-Next IQ3_S, so the results are comparable. The machines are named after their hardware level:

The agent itself detects a new Strata release, downloads it, runs the measurements and, on request, optimizes the configuration. All optimization runs locally, using the same Qwen3.8-Flash-Next IQ3_S model on the latest Strata version.

P1005 (Tesla P100): from data-starved to compute-bound

The model experts total 46.8 GiB, too big for RAM, and the 16 GB card was so full that the engine warned that decode would fall to a few tokens per second. Following the Strata repository documentation, the agent changed four things:

--vram-reserve-mib 960        (was 700)
--max-context 65536          (was 262144)
STRATA_Q8_SM60=0
--resident-experts
STRATA_DENSE_F32=1

Result: GPU utilization went from 27% to 92% (155–170 W). Prefill became up to 4.4× faster; decode +40% at 8K and 2.4× at 16K.

ContextBefore (prompt / decode, tok/s)After (prompt / decode, tok/s)
51247.7 / 13.454.5 / 14.3
2K62.6 / 10.374.5 / 13.9
8K46.4 / 9.9178.1 / 14.3
16K43.8 / 6.2193.9 / 15.1
32K44.1 / 6.0213.8 / 12.6

Values are prompt / decode tokens per second. The cost: 24 GiB of RAM is now page-locked for experts, so nothing else large should run on this machine, and the context cap is 65K instead of 262K. Everything persists across reboots.

P2002 (Radeon RDNA4): live tuning, then a short restart

First, live tuning without restarting the engine. The CPU governor set to performance and a longer page cache for experts were kept; pinned GPU clocks reduced prefill by about 10% and were rejected; larger read-ahead had no effect. Decode at 2K and 8K improved by 10–18%.

Then, with a restart of about 40 seconds (the fallback chain carried the session, with no visible interruption), the agent raised the VRAM reserve from 700 to 960 MiB and enabled --kv-grow, keeping the full 262K context. Expert slots grew from 2518 to 3686 (+46%), the expert hit rate rose from 74% to 87% and the paging warnings disappeared. It also added a watchdog so the engine restarts on its own.

ContextBefore (prompt / decode, tok/s)After (prompt / decode, tok/s)
512547 / 63.6602 / 57.5–64
2K1228 / 60–711275–1303 / 66–74
8K2085 / 59–691723–2144 / 79–82
16K2180 / 72.71988–2169 / 76–78
32K2056 / 72.92023–2096 / 76–77

Standard suite: chat decode 74.3 tok/s (was 71.9), first token 0.39 s (was 0.46), agent decode 66.7 tok/s (was 59.2). The agent also noted honestly that the first numbers right after a restart are about 25% low because the expert cache is still cold.

Mac Studio (M3 Ultra): the defaults were already optimal

The agent restarted the engine six times for clean A/B runs and proved empirically that the default configuration was already the best one. KV options had no effect on unified memory; a large wired expert cache was harmful (decode collapsed to about 32 tok/s) and was reverted. Prefill of about 790 tok/s is the bandwidth limit of the hardware, not of the configuration. Final suite: chat decode 69.1 tok/s, first token 0.48 s. All dead ends were documented so nobody repeats them.

New releases, measured

DeepSeek V4.1-Flash running locally

DeepSeek V4.1-Flash, a large MoE model, now runs locally on Strata: the hot experts stay in RAM and the rest is streamed from the SSD. We measured 14 tok/s decode. On our current hardware this is not enough for the main brain of the agent, but it works well as a second-opinion model and overnight auditor.

What this means for a Box customer

Original thread on X · All news