Skip to content

Qwen3.8-Flash-Next on any consumer hardware: one-click install for Windows / Linux. Strata inference engine, OpenAI/Anthropic API on localhost, optional image input.

C++

Release notes 0.2.1: the #3237 drive probe is on by default (owner OK)

Niko1221a7bdbfdabc9a
diff --git a/docs/release-notes-0.2.1.md b/docs/release-notes-0.2.1.md
index 1a9c973de..635b9a865 100644
--- a/docs/release-notes-0.2.1.md
+++ b/docs/release-notes-0.2.1.md
@@ -46,7 +46,7 @@ Speed numbers are medians of interleaved pairs on the same box, a fresh engine p
- **AMD RX 9000 / R9700 on Linux: the engine opens its GPU queues in a fixed order at start.** Before, about half of the fresh engines with MTP read prompts 8 to 14% slower, depending on which compute pipe the card's firmware gave the engine's two busiest queues (both on one pipe was slow). The engine now opens two queues on its main thread before anything else starts. Measured on two Radeon AI PRO R9700 boxes (Linux, ROCm 7.10, Q2_0 with MTP): without the fix 10 of 32 fresh starts read the 4K prompt under 2,000 tok/s (about 2,290 for a fast start); with it 0 of 32. Decode against the fix switched off, 20 interleaved rounds: 1.000 / 1.001 / 1.000 (story / code / facts). Opening more queues cost decode (five queues: 2 to 3.6% slower), so two is the default. Same answers: the identity gate (10 prompts, 4K and 20K exact checks) is identical for Q2_0 and IQ3_XXS, also with the 0.2.0 prompt defaults on. `STRATA_HIP_QUEUE_PRIME=0` turns it off. One card was measured; Windows and RX 7000 cards are not changed.
- **Linux hybrid CPUs with low-power E cores (Core Ultra "Meteor Lake" / "Arrow Lake-H", #3262).** The engine and setup now count the cores listed in `cpu_lowpower` as efficiency cores. A Core Ultra 7 255H used to look like 8 P and 8 E cores, so the hybrid plan did not apply and 15 workers ran; it now plans 10. The reporter measured the 15-worker default about 35% slower than 9. We have no such CPU and ran unit tests only (the plan and a fake `/sys`); only the number of workers changes, not the answers.
- **Two GPUs of different architectures (HIP): no start-up warm-up (#3204).** The warm-up product that runs on every card at start made prompts about 25% slower on a split of gfx1151 and gfx1201 for the reporter (`STRATA_PREFILL_WARM=0` restored them). It now runs only when every visible card has the same architecture. We have no mixed pair; on two R9700 (same architecture) the warm-up costs nothing (3,855 against 3,853 tok/s at a 32K prompt, 5 pairs), so the change leaves them as they were. The first request on a mixed pair pays the 1 to 2.5 s library load again, as before 0.2.0. `STRATA_PREFILL_WARM=1` / `0` overrides.
-- **Linux, models read in place: a drive probe decides between the file cache and unbuffered reads (#3237). Pending owner OK; not final for the release.** The room rule picks the file cache when RAM seems to have room, which was 2x slower in prompts and 3 to 4x slower in decode for a reporter with a PCIe 5 drive (about 8 GB/s). When the rule says "cache" and the cache would hold under half of the reads, the engine now reads 96 random 1 MiB pieces both ways at start (under 2 s) and goes unbuffered only if the drive reads at least 4 GB/s and is faster that way. Every drive we have (1.6 to 3.1 GB/s) keeps the file cache; on a 2 GB/s NVMe the cache was better for decode (up to x1.6) and unbuffered reads better for prompts, the opposite of the report. Untested on a fast drive; the answers cannot change (only where reads go), and no identity gate was run. `STRATA_FILE_TIER_PROBE=0` turns it off.
+- **Linux, models read in place: a drive probe decides between the file cache and unbuffered reads (#3237).** The room rule picks the file cache when RAM seems to have room, which was 2x slower in prompts and 3 to 4x slower in decode for a reporter with a PCIe 5 drive (about 8 GB/s). When the rule says "cache" and the cache would hold under half of the reads, the engine now reads 96 random 1 MiB pieces both ways at start (under 2 s) and goes unbuffered only if the drive reads at least 4 GB/s and is faster that way. Every drive we have (1.6 to 3.1 GB/s) keeps the file cache; on a 2 GB/s NVMe the cache was better for decode (up to x1.6) and unbuffered reads better for prompts, the opposite of the report. Untested on a fast drive; the answers cannot change (only where reads go), and no identity gate was run. `STRATA_FILE_TIER_PROBE=0` turns it off.
## Fixes from user reports