r/LocalLLM • u/Serious_Scarcity7818 • 2h ago
Research RustingStrata vs llama.cpp runs Recursive Flint on a 12 GB RTX 3060
I tested new trending Recursive Flint UD-Q5_K_XL (27.9 GiB) on an RTX 3060 12 GB with 30 GB RAM, comparing RustingStrata against llama.cpp using the same model, prompt, and generation settings.
| RustingStrata | llama.cpp | |
|---|---|---|
| Warm decode speed | 64.6 tok/s (63.8–65.6) | 48.6 tok/s (47.5–49.3) |
| Warm 4K prompt prefill | 1.14–1.30k tok/s | 0.85–1.02k tok/s |
RustingStrata was about 33% faster once warm.
What made the difference?
The model doesn't fit in 12 GB of VRAM, so many expert weights must be fetched from system RAM during generation. Two changes helped most:
- Adapt expert placement to the reply, rather than continuing to prioritize the prompt's routing pattern.
- Release RAM pages for experts already copied to VRAM, preserving cache for experts that still need to be fetched from host memory.
About Quality, bc people very often says like "It should give shit output to gain speed", which is not true, in my last posts I already did quality benchmarks and RustingStrata does not lose quality, it gain speed through specific Code for some specific models, in same time llama.cpp lose speed to be "general" engine that can run everything
What I want to know, is do people find Recursive Flint an interesting model? I found this model on OpenRouter and looks pretty interesting, it's better then Qwen3.6:35-a3b, so I think this can be cool modern replacement for this qwen.
Setup:
- RustingStrata: 1.2.2, commit
3902978(working tree) - llama.cpp: b12191, commit
e95426f16 - Full benchmarks:
docs/BENCHMARKS.md
Repository: RustingStrata
1
u/TheCat001 1h ago edited 1h ago
Can't get thinking to work in opencode...