Context: we ran what we believe is the first independent benchmark of Ternary Bonsai 27B on consumer hardware (RTX 5060 Ti 16 GB, fork commit b9591, CUDA build for sm_120, Linux). Overall results were good for the fork: ternary +24-31% decode vs a best-engine IQ2_XXS baseline, 262k context fits a 16 GB card with q4_0 KV, and the DSpark lossless-precision claim verified byte-identical Q4_1 vs bf16 (5/5 prompts at temp 0). Raw data and scripts: https://github.com/Astezelex/bonsai-27b-16gb-bench (also PrismML-Eng/Bonsai-demo#98). This report is friction we hit on the way.
The fork docs say a q4_0 K-cache "wants" a --kv-mean-center bias file for quality, but there is no guidance on generating or obtaining one per model, and no shipped file for Bonsai 27B. At 262k context (the fit headline for 16 GB cards) q4 KV is mandatory, so the quality delta matters.
Could you document the workflow (how to produce the bias file for a given model), or state that it is safe to omit for Bonsai 27B?
Context: we ran what we believe is the first independent benchmark of Ternary Bonsai 27B on consumer hardware (RTX 5060 Ti 16 GB, fork commit b9591, CUDA build for sm_120, Linux). Overall results were good for the fork: ternary +24-31% decode vs a best-engine IQ2_XXS baseline, 262k context fits a 16 GB card with q4_0 KV, and the DSpark lossless-precision claim verified byte-identical Q4_1 vs bf16 (5/5 prompts at temp 0). Raw data and scripts: https://github.com/Astezelex/bonsai-27b-16gb-bench (also PrismML-Eng/Bonsai-demo#98). This report is friction we hit on the way.
The fork docs say a q4_0 K-cache "wants" a
--kv-mean-centerbias file for quality, but there is no guidance on generating or obtaining one per model, and no shipped file for Bonsai 27B. At 262k context (the fit headline for 16 GB cards) q4 KV is mandatory, so the quality delta matters.Could you document the workflow (how to produce the bias file for a given model), or state that it is safe to omit for Bonsai 27B?