Siliang Engine v0.1.4 (Experimental)
Pre-release
Pre-release
Siliang Engine v0.1.4
v0.1.4 is a correctness and Windows release-packaging hotfix on top of v0.1.3.
It does not introduce new model-performance claims or change the recommended
v0.1.3 model profiles.
What changed
- Fixed a cross-request K/L2 ownership bug in the SLFU hot-demotion path. With
K-prefill disabled, prompt processing for a later request can legitimately
repopulate L2 with an expert that is still warm in K from the preceding
decode. A later K eviction used to attempt a second L2 store for that expert
and fail closed withduplicate-resident. The transition worker now
quiesces L2 before ownership changes and reuses an already-resident L2 copy
instead of creating a duplicate. - Expanded fail-closed K/L2 diagnostics so rejected victim stores report the
rejection stage, layer, expert, and slot rather than collapsing into a
generic swap failure. - Enabled the embedded llama.cpp Web UI in Windows release builds. Release
builds first build the UI from source with npm, may fall back to the verified
prebuilt UI source, and fail the build ifLLAMA_UI_HAS_ASSETS=1is not
present in the generated UI header. - Persisted runtime CPU-dispatch evidence in packaged release provenance so the
selected packaged CPU backend remains auditable after CI packaging.
Release qualification
The v0.1.4 hotfix was qualified on the Windows CUDA reference workstation with
fresh CPU and CUDA builds.
- Fresh Windows CPU Release build: completed; embedded Web UI verified.
- Fresh Windows CUDA 13.2
sm_75qualification build: completed; embedded Web
UI verified. - Embedded Web UI runtime smoke:
GET /returned HTTP 200 with embedded HTML. - DeepSeek V4 Flash K/L2 multi-request regression:
- request 1: 128/128 decode tokens, ~1.74 tok/s;
- next prompt: 221 tokens processed on the same server process;
- request 2: 32/32 decode tokens, ~1.61 tok/s;
- no
duplicate-resident, K/L2 transition failure, fail-closed event, or
compute error was observed.
The throughput values above are smoke-test observations only. v0.1.4 retains
the model qualification and limitations documented for v0.1.3; see
v0.1.3.md for the broader performance evidence.
Compatibility and boundaries
- The public expert-cache configuration remains the v0.1.3 typed CLI/server
interface. - Existing v0.1.3 model recommendations remain unchanged.
- Use
--parallel 1whenever L1 K/R/P is enabled. - L1 K/R/P remains intentionally incompatible with LoRA in this prototype.
- The Siliang expert arena remains Windows-only; Linux CPU and macOS Metal CI
continue to protect the upstream-compatible non-arena paths.