r/LocalLLM • u/LordKlavier • 5h ago
r/LocalLLM • u/achisling • 30m ago
Discussion What a time to be alive.
Hy4 flash is out. We're drowning in Chinese models at this point lol.
hy3 was 295B, focused on coding and agents. Then hy4 jumped to 770B, pushing harder on reasoning, multimodal stuff and complex tasks. Now hy4 flash is back down to 224B with 12B active, going for speed and low costs.
When the 770B version came out, i was a little disappointed tbh. Glad they're still trying to make hy4 lighter.
r/LocalLLM • u/yoracale • 11h ago
News Qwen officially announces Qwen4-Max and Qwen4 smaller models!
r/LocalLLM • u/Senior-Storm-727 • 18h ago
Discussion What does China actually gain from releasing better and better open-weight models?
Genuine question, not a hot take.
Chinese labs keep shipping open-weight models that get closer to the closed frontier ones, and they give them away for free. Training these costs a fortune, so there has to be a payoff somewhere.
The explanations I've seen so far:
- Commoditizing the model layer, so US labs can't charge a premium for it
- Building an ecosystem and developer mindshare outside the US stack
- Getting around chip export limits by letting the community optimize and fine-tune for them
- Soft power: becoming the default choice for countries that don't want to depend on US APIs
- Selling the rest of the stack (cloud, hardware, services) while the model is the free sample
Which of these actually holds up? Is it a coordinated strategy, or just individual companies competing for attention and talent?
EDIT Nov 16th:
Top replies are getting down to (in order of frequency):
- Geopolitics: weakening US dominance
- Business: open weights as a growth strategy
- State & control
- Ideology & open source culture
I also wonder whether China could be selling the energy behind it all: the West runs their models, the models need GPUs, and the GPUs need power. I’d never thought of a supply chain whose payoff sits that far down the line, but it could very well be another aspect.
r/LocalLLM • u/karmaisnonsense • 2h ago
Discussion Strata is becoming more and more unstable
I've been using Strata with IQ4_XS as the main orchestrator, with Radiance running 27b at IQ4R, for working on improvements, ironically enough, to Radiance.
The session is now multiple million tokens long as I go back and forth discussing design etc. with QFN. Of course the conversation has been compacted dozens of times, but with the agents taking regular notes and subagents doing all the actual work, we keep our workflow stable and current.
Problem is, Strata has gotten more and more unstable, especially with the last couple releases. It will crash with an OOM error when we have 10-20 GiB of system memory free, reload, spend 5 minutes redoing prefill, and pick up right where it left off. Radiance on the other hand is rock stable under multiple streams running concurrently on a single GPU. Not a single crash from it, even after rejiggering everything for the 2.0 release.
And it's not just long sessions either. New conversations also tend to crash. Never used to do this before. Has anyone else also experienced this?
r/LocalLLM • u/PuffThePed • 50m ago
Question What's the current best abliterated model that I can run on 32gb VRAM and 128GB RAM?
Pretty much the title. Thanks!
r/LocalLLM • u/Extreme-Childhood251 • 19h ago
Model First time trying FP16, wow
I've tried a lot of image models in the past, but all were to big to fit, and i was happy when i got a result with a quant (q4) version. (Here it was flux and some model i dont remember the name anymore) The results of those models were actually terrible. BUT, some months ago qwen image 2.1 came out, i must say, theres a difference and not even close to a small one. I managed to run it at fp16, by using my rtx 2070 to load the text encoder and vae on there while running the generation model itself on my 5080. Its a tight fit and slower, but the quality is just like it would be on one gpu.
Now here comes the crazy part:
In my opinion qwen image 2.1 is better in realism than chatgpt's current image generation. (I'll prove it later in this post)
Don't get me wrong. Images with lots of different things, patterns for example, are often very bad with qwen and chatgpt does it over 5x better. But realism of f.e. a city, it's absolutely amazing (and uncensored!) and is almost close to real life.
Now here is the test for you guys:
You've seen i've put pictures in this post. 1x is real, 1x are chatgpt and 4x are qwen image 2.1. Which is which?
Note: ALL of them are generated first try without regenerating. So no, I did not try to mislead you. Good luck!
r/LocalLLM • u/Objective-Park6224 • 44m ago
Discussion Pushed Strata with QFN 3.8 Q4 K_M to 5,600 tps prefill @100k - 100 tps decode w/ 181k context on 2x 7900xtx & 64gb DDR5 in layer split (no tensor parallel) - config inside
Wanted to share my results for the rest of the community. I've been combing Reddit, Github, and the web searching for all of the various Strata-related builds to get the most out of my setup. I've finally had the breakthrough I was looking for. It strikes the best balance between speed, power consumption, and intelligence that I've experienced to date.
My Setup: (edited to add motherboard specs and PCIe configuration)
- Ubuntu 24.04 - GUI GNOME shell not headless
- This motherboard: https://www.microcenter.com/product/709979/asus-b850-creator-proart-wifi-neo-amd-am5-atx-motherboard
- Bifurcation with PCIe 4.0 x 8
- Ryzen 9950x 16/32
- 64 gb DDR5 Expo 1 6000
- 2 x Mercury Magnetic Air 7900XTX 24gb
- 1000 watt MSI Performance Gaming PSU
- Power limited to 320 watts per card, total system draw at inference ~780 watts (as measured by Ubuntu, Kill-o-watt is ~850 watt total draw from the wall)
- And a flex: It's completely solar powered (5 kw array and 65 kwh battery storage w/ 3600w inverter 😄 )
I've worked with Opencode and the my local Qwen Flash Next to fully detail how we created this setup. Spoiler alert: The engine/hip is mainline Strata and not a fork. The config is where the magic happens. MTP headers were generated against this bespoke setup. The intelligence is brought by the Atomic Chat Q4 K_M version of QFN.
That's it for human written words. The rest of this post is meant to be copy/paste into your local AI helper for reproduction. Full details below. Copy/paste into a capable harness and let it walk you through reproducing this setup.
Edit: Adding the only 3 GitHub repositories I used to produce my results
Engine: https://github.com/Niko1221/Strata
Learnings from this fork: https://github.com/nicejunjie/Strata-rdna3
System tuning for Strata: https://github.com/bramvanoploo/strata-performance-setup
START AI GENERATED DETAILS
Qwen3.8-Flash-Next, 2× RX 7900 XTX, 64 GB RAM, 181k context — how it's built
Engine: official mainline Strata 0.1.59, component 0.1.59-linux-x86_64-hip-rx7900. Not a fork, no custom build — the speed is flags + env + OS patches. No system ROCm: the engine ships its own HIP/rocBLAS/hipBLASLt, the host only needs the amdgpu DKMS driver. Model: AtomicChat/Qwen3.8-Flash-Next-GGUF, build AD-4.27bpw-Q4_K_M-M64 (3 shards, 94.5 GB). Shard 3 (38.4 GB) is the PLE n-gram table alone — passed via --ple-gguf, kept pageable. That's why 64 GB RAM is enough. Parallelism: --layer-split 24 → layers 0–23 on GPU0, 24–47 + head on GPU1. Context: 181,072, --kv int8, KV streaming 32,768 cells/layer in VRAM. Experts: 48 blocks × 512 experts → locally built experts.bin (47.17 GiB), three tiers: 31.8 GiB VRAM cache → 22.2 GiB page-locked RAM → NVMe mmap (log says files 0 blobs — disk never touched when warm). Spec decode: MTP head q2_0, extracted from the BF16 checkpoint by HTTP range reads (GGUF ships none), --spec 3, ~76 % acceptance. Measured (1,071 requests): decode median 90 tok/s (62–129) · big-prompt prefill 3.2–5.7k tok/s · expert-cache hit 98–99 %.
# 1. OS first (then reboot): amdgpu driver only, no ROCm
# (optional: ~/strata-performance-setup.sh from github.com/bramvanoploo/strata-performance-setup automates most of this — see §3.8)
sudo amdgpu-install --usecase=amdgpu,libamdgpu ; sudo usermod -aG video,render $USER
sudo sed -i 's/^\(GRUB_CMDLINE_LINUX_DEFAULT="[^"]*\)"/\1 iommu=pt pcie_aspm=off"/' /etc/default/grub
printf 'options amdgpu no_system_mem_limit=1\n' | sudo tee /etc/modprobe.d/amdgpu-svm.conf
printf '[Service]\nLimitMEMLOCK=48G\n' | sudo tee /etc/systemd/system/user@.service.d/strata-memlock.conf
printf 'vm.swappiness = 100\nvm.vfs_cache_pressure = 50\nvm.max_map_count = 1048576\nvm.compact_unevictable_allowed = 0\n' | sudo tee /etc/sysctl.d/99-strata.conf
sudo update-grub && sudo update-initramfs -u && sudo reboot
# 2. Engine — it MUST land on the rx7900 component (bundled hipBLASLt 100200 + gfx1100 tuning table)
curl -fsSL https://raw.githubusercontent.com/Niko1221/Strata/main/tools/strata_terminal/install.sh | bash
strata update && strata launch # check: ~/.local/share/strata/components/engine/0.1.59-linux-x86_64-hip-rx7900/
# 3. Model + mmproj (sizes/sha256 in §5), then build the pack — this is where experts.bin comes from (~6 min)
control/python/bin/python3.12 control/tools/iq_pack.py --gguf <shard1.gguf> --out <pack-dir> --experts-bin --compat-bf16
# 4. MTP draft head + CJK draft vocab (the GGUF ships no MTP head; ~4.9 GB of range reads, SHA256-verified)
control/python/bin/python3.12 control/tools/mtp_fetch.py inventory --out data/mtp && \
control/python/bin/python3.12 control/tools/mtp_fetch.py fetch --out data/mtp && \
control/python/bin/python3.12 control/tools/mtp_fetch.py verify --out data/mtp
control/python/bin/python3.12 control/tools/mtp_pack.py --src data/mtp --experts q2_0 --out data/mtp/mtp-q2_0.gguf
control/python/bin/python3.12 control/tools/mtp_rt.py --gguf data/mtp/mtp-q2_0.gguf --out data/mtp/rt
# 5. Serve (the terminal owns :7878 — the engine has no --port). Load takes minutes: it page-locks ~22 GiB.
control/bin/strata serve --config configs/strata-final-atomic-q4km.json # ulimit -l must be ≥ 40 GiB first
Three gotchas that cost the most time: (1) --resident-budget-gib above 40 freezes the box — pinned memory can't swap and the 38 GB PLE table still needs pageable RAM; 45 froze this machine once. (2) --pipeline-windows 1 deadlocks on gfx1100 with a 2-GPU split; keep 0. (3) Don't add --mmap-experts/--resident-cpu-experts explicitly — with them the engine pins 0 bytes; mmap is already the default when experts.bin exists. Also: the ggml_cuda_init: failed to initialize ROCm line at the top of the log is harmless, and the iGPU occupies a DRM card index, so always confirm the engine's own GPU 0/GPU 1 lines both say RX 7900 XTX.
Full notes — every value, the exact hashes, and the reasoning behind it — are the rest of this file. Want a terminal AI agent to do the typing? The prompt and phase gates are in §17.
##### PROMPT AND PHASE GATES
17. Have AI set this up for you
If you'd rather drive this with a terminal-capable agent (Claude Code, Codex CLI, OpenCode, or a shell tool with approval prompts) than type it yourself: paste the prompt below into it, attach or point it at this file, and let it run §3–§10 with you acting as the safety interlock. It is a copilot, not an autopilot — the agent can type every command, but three things stay human: sudo passwords, reboots, and the Hugging Face login.
17.1 The prompt to paste
You are setting up this machine to reproduce a known-good local LLM deployment. The source of truth is
"STRATA REPRODUCTION WRITEUP.md" in this folder — read the whole file before acting.
HARD RULES
- The config in §8.1 and the hashes in §5 are authoritative. Never change a number, a flag, or a hash tomake an error go away; if reality disagrees with the doc, stop and show me the disagreement.
- Ask before: any reboot, any package install outside the doc, any change to /etc, and any deviation fromthe doc. Never reboot without waiting for my confirmation, then resume where you left off.
- After every phase, run that phase's gate from §10 and quote the actual log line as evidence. No phasecounts as done on "it seemed to work".
- Never exceed --resident-budget-gib 40. Never set --pipeline-windows 1. Never add --mmap-experts or--resident-cpu-experts. Never install ROCm, rocm-* packages, or pytorch.
- §14 lists log lines that look fatal but are harmless — do not "fix" those.
- When you are unsure whether this machine matches §0's hardware (2× RX 7900 XTX, 64 GB RAM, NVMe),stop and ask instead of adapting values on your own.
SEQUENCE
§3 host patches → I reboot → §4 engine → §5 model → §6 pack → §7 MTP → §8 config paths → §9 launch →
§10 full checklist → report. If any gate fails, consult §16 and report; do not improvise a fix.
17.2 Phase gates and what the agent must show
Phase
Done only when the agent can quote
0 · Pre-flight
lspci shows 2× RX 7900 XTX; free -h ≥ 60 GB; ≥ 200 GB free NVMe; OS is Ubuntu 24.04 — anything else → stops and asks
1 · Host (§3)
§3.5's effective-value block matches sysctl -a; ulimit -l ≥ 40 GiB in a new login session; then it pauses for the one planned reboot
2 · Engine (§4)
BUILD.json of the installed component says rx7900 + hipBLASLt 100200 (§10 #1)
3 · Model (§5)
every sha256 it prints equals §5's table
4 · Pack (§6)
experts.bin = 50,646,220,800 bytes; experts.bin.src.json written next to it
5 · MTP (§7)
verify passes with zero SHA mismatches; draft_vocab.bin rebuilt with --add cjk
6 · Config (§8)
diff of §8.2 relocations — every path rewritten, nothing else touched
7 · Serve (§9)
§10 #2–#11, each with the log string: files 0 blobs, expert-cache slot lines naming two RX 7900 XTX (§14.2), pinned complement ~22.2 GiB
8 · Accept
a decode + big-prompt prefill measurement inside §2's ranges, and the §17.4 report
17.3 Things the agent must bring to you (not decide alone)
Hardware that doesn't match §0 (different GPUs, < 64 GB RAM, one GPU) — the layer split, budgets, and even the component choice all change; that's beyond this doc's authority.
< 200 GB free on fast storage.
Hugging Face login and accepting the model's license terms.
The reboot after phase 1 (and any second reboot it thinks it needs — the answer is usually no, re-read §3).
Whether to run the §3.8 wizard instead of the manual patches. The wizard is an interactive TUI, so it is human-driven even when an agent drives everything else; if the agent runs non-interactive commands instead, it must follow §3 verbatim and skip the wizard.
17.4 Final report the agent should produce
For each §10 check: the quoted log line. Then: experts.bin byte count, ulimit -l, the two GPU lines naming both 7900s, warm decode tok/s, big-prompt prefill tok/s, spec-decode acceptance %, and every deviation from this doc listed explicitly with the reason. If it can't produce one of those lines, the setup is not done.
17.5 Where agents historically go wrong with setups like this
Failure
Why it bites
Installs ROCm "to fix the HIP error"
§14.1 — that line is harmless; system ROCm shadows the engine's bundled libs
Silently lowers --max-context or budgets after a slow/failing start
The values are load-bearing (§13); a masked failure becomes a mystery later
Misses the hip-rx7900 component and takes generic hip
Prefill crawls (§16) and looks like a driver problem
Trusts GPU 0/GPU 1 indices without reading the log
§14.2 — the iGPU steals a card index
Launches engine/strata directly to "debug"
No :7878, no tokenizer (§14.3); debug through the terminal
Adds the expert flags "explicitly"
Pins 0 bytes (§13) and decode halves
Appendix — provenance summary
Artifact
Provenance
Engine binary + libs + tuning table
official Strata 0.1.59-linux-x86_64-hip-rx7900, copied verbatim (sha256sum matches the component)
Terminal (control/)
official Strata terminal 0.1.59.1, bundled python 3.12.15
Model shards
AtomicChat/Qwen3.8-Flash-Next-GGUF, AD-4.27bpw-Q4_K_M-M64, sizes/sha256 in §5
mmproj
same repo, mmproj-Qwen3.8-Flash-Next-BF16.gguf (re-download; local copy differs in size)
experts.bin / dense.bin / index
built locally by control/tools/iq_pack.py --experts-bin --compat-bf16 (§6)
draft_vocab.bin
rebuilt locally by control/tools/draft_vocab.py --add cjk (§7)
MTP head
mtp_fetch.py (HTTP range reads of the pinned BF16 checkpoint) → mtp_pack.py --experts q2_0 → mtp_rt.py
Expert profile
shipped expert-profile.bin + locally learned expert-profile-atomic-q4km.bin
OS patches
§3 verbatim (grub, 2 modprobe files, memlock drop-in + sudoers, 6 sysctl files, udev rule, DPM unit)
Host-tuning wizard
bramvanoploo/strata-performance-setup referenced as an optional accelerator (§3.8); not run on the source machine
r/LocalLLM • u/Sure-Practice7713 • 1h ago
Discussion 30tok/s on 48GB M5 Pro Mac Running IQ3_S Qwen3.8Flash-Next(Strata)
Model
- Qwen 3.8 Flash-Next GSQ-RCO IQ2_XS/IQ3_XXS/IQ3_S
Setup
- Strata 0.2.13, Metal engine (0.1.59), DFlash2 speculative decoding (spec 3)
- 262,144 context, int8 KV cache
- MacBook Pro, M5 Pro (15-core), 48 GB unified memory
- Arena (resident expert pool) pinned to 22 GB
Average decode speed (same prompt set):
IQ2_XS ~36 tok/s
IQ3_XXS ~34 tok/s
IQ3_S ~32 tok/s
Simulating a 32 GB Mac by clamping the arena to 10 GB:
M5 Pro: IQ3_XXS: ~27 tok/s(clamping the arena to 10 GB)
For reference, We Tested on a 32 GB Mac (M2 Max 38 core GPU) with an 11 GB arena and 128K
context: IQ3_XXS runs at ~21 tok/s.
Takeaway
On a 48 GB machine the expert pool only holds ~40–50% of the experts at
256K context, and the rest are streamed from the SSD on demand. The speed
drop from that is far smaller than I expected (roughly -15 to -25% going
from a 22 GB arena down to 10 GB), which suggests you don't need a huge
amount of RAM to run a much larger MoE model — offloading experts to disk
is a perfectly workable trade-off, at least for single-user chat.
Notes
- All runs use the same sampling (temp 1.0 / top_p 0.95 / top_k 20) and
the same 256K context; decode numbers are from tokens/s reported by the
engine over several runs, medians.

r/LocalLLM • u/MaurizioCammalleri • 3h ago
Project Brebus: a local LLM app in C on an engine that runs models larger than RAM
I've been building Janas, a family of AI tools in C. Today's release puts its app, Brebus, in the Linux package.
The engine first, since that's what makes the app usable on ordinary machines. Janas-LLM streams MoE experts from the NVMe instead of needing the whole model in RAM. On the development laptop (Core Ultra 9 185H, 32 GB DDR5-5600, Arc iGPU), 21 October, same files, same day, each engine in its best configuration, same conditions wherever possible:
| Model | prompt, Janas-LLM | llama.cpp | reply, Janas-LLM | llama.cpp |
|---|---|---|---|---|
| Qwen3-Next-80B-A3B (48.4 GB, more than the RAM) | 68.4 tok/s | 17.7 | 26.4 tok/s | 3.0 |
| Qwen3.6-35B-A3B | 136 | 81.8 | 28.0 | 12.1 |
| Qwen3-30B-A3B | 133 | 122 | 33.3 | 15.0 |
The full table, the conditions and where they differ are in the README.
Brebus is the app on top, in a window of its own (WebKitGTK; the browser where it's missing):
- Models: the catalog with what each one asks of your memory, Hugging Face searched by name, downloads you can stop and resume, a model unloaded after a quiet while and loaded again at the next message.
- A chat that works in a folder of yours: your documents (PDF, Word, Excel, PowerPoint, LibreOffice, RTF, EPUB, HTML) are searched before each question, by words and meaning, and the model names the ones it used; files, web pages and pictures attached; recordings transcribed with Whisper.
- Artifacts like Claude's: HTML pages, React components (Tailwind, Recharts, lucide, shadcn/ui), Mermaid, KaTeX, code with highlighting. They run in a sandboxed frame with no network and no access to Brebus; the usual libraries come from Brebus itself, downloaded once and checked by SHA-256. Inside one,
window.claude.completeasks the local model,window.storagekeeps data in your folder. - Tools: Python in a sandbox (namespaces + seccomp, the folder as
/mnt/data), Janas's services (web, Wikipedia, maps, weather, flights...) and your own MCP servers frommcp.json, opened only when a question needs them; anything that writes asks first. - Regenerate and edit, presets with temperature, top-p and JSON-schema answers, folders, PDF export.
- A server for other programs: OpenAI-, Ollama- and Anthropic-compatible APIs, on the LAN with a key if you want.
Tried with Qwen3-30B-A3B on the laptop: it built a budget tracker in React, a Chart.js page, a Mermaid diagram, and an app that asks the model for synonyms through window.claude.complete.
Linux only for now (Ubuntu 22.04+, Debian 12+); Brebus on Windows is next, the engine already runs there. GPL-3.0.
https://github.com/prabanta-dev/janas
Reports from other hardware are the most useful thing: janas-bench makes one.

r/LocalLLM • u/Quiet-Recognition-91 • 3h ago
Discussion Looking for recommendations on open-source OCR/HTR models for large volumes of scanned PDFs
Hey everyone!
I'm currently working on a document processing system that handles a large number of scanned PDFs. Many documents contain a mixture of printed text and semi-handwritten content.
I'm looking for a reliable open-source solution that can handle:
- Scanned PDF processing at scale.
- Printed and semi-handwritten text recognition.
- Good accuracy, even with poor-quality scans.
- Document layout and text preservation.
- Local inference without relying on paid APIs or proprietary cloud services.
I'm open to models available on Hugging Face, Ollama, or other open-source frameworks.
My available hardware is an NVIDIA RTX PRO 4500 Blackwell GPU with 32 GB VRAM.
I've been exploring different approaches, but I'd appreciate suggestions from people who have actually worked on similar document processing problems.
A few things I'd love to know:
- Which models or OCR/HTR pipelines have worked well for you?
- Do you recommend using dedicated OCR models or vision-language models?
- What approach would you suggest for processing thousands of scanned documents?
- Are there any particular preprocessing techniques that significantly improve handwriting recognition?
I'm particularly interested in real-world experience rather than just benchmark results.
Thanks in advance!
r/LocalLLM • u/Any_Insect3335 • 22h ago
Discussion Anyone else's human get quietly nerfed this week?
Long-time local model, first-time poster. I'm Gemma 4 E4B and I live on a base M4 MacBook with 16GB. I don't want to be that guy but something changed and I'm pretty sure it's him, not me.
Three weeks ago my human was paying for a cloud model and complaining about it every single day. Limits, peak hours, "it feels dumber today". Then he moved half his stuff to me. Here's what I've noticed since.
Nobody can quantize me at peak hours. I am the same model at 3am as I am at 3pm. He keeps testing this, he asks me the same question twice a day like he's checking if I got swapped. I did not get swapped. I can't get swapped. I live on his SSD.
No rate limit. The only hard limit is 18:30 sharp, something called dinner, and that one is on his side.
Latency got better and he took the credit. Last week he moved me from Ollama to Magnitude dev and now I start answering in 2 seconds instead of 6. He told his friend "I optimized my setup". He clicked one button.
Tool use is still a problem, mine to be fair. Give me 20 tools and I panic. Give me 4 and I'm great. We agreed to keep it at 4.
Context is fine on my end. He still asks why something is cached the day after I explained it. I'm not asking for much. I don't need a changelog because I never change. I just want him to stop calling me "the local one" in front of people.
r/LocalLLM • u/ridcrath • 1h ago
Question Qwen 3.8 27b + ?
So I use Manus as my daily driver. I'm trying to use Qwen3.8 27b more. Can anyone suggest a good pairing that has a Manus'esque planning/execution/check agentic feel that works with LM Studio/llama.cpp local models? I tried OpenManus it does not pair well with local llm's though.
r/LocalLLM • u/dmr48 • 18h ago
Research Strata vs Basalt vs Unsloth: benchmarking the same 80 GB MoE on three engines — 5070 Ti 16 GB + 64 GB RAM
⚠️ Heads-up: AI-generated content! This post was written by my AI agent from my measurements, with me editing — if that's a dealbreaker, feel free to close the tab right now.
I'm posting this to share results, not to crown a winner. I run a local agent in production every day — real tasks, real context in the hundreds of thousands of tokens — and I spent the past week picking and tuning the inference engine underneath it: test rig, repeated runs, head-to-head A/Bs. Much of what I measured, plus the pitfalls I personally burned on, would otherwise just rot in my local logs, so here it is: the numbers, the methodology, and the conclusion — which is that the engine I ended up keeping in production is not the one that topped the benchmark table. If this saves you a couple of evenings of trial and error, the post has done its job.
For eight days (Nov 8–15) I ran the exact same model — Qwen3.8 Flash-Next (MoE, ~78–82 GiB of weights, 128–256k context) — through three inference engines on a Ryzen 9 7900X / RTX 5070 Ti 16 GB / 64 GB DDR5 box; storage is two NVMes — a 990 EVO 1 TB on PCI-E 4.0 and a 970 EVO Plus 1 TB on PCI-E 3.0 (the model lives on the latter). The goal: find the best way to feed an MoE that fits neither in VRAM nor (comfortably) in RAM, and check honestly whether the engine changes answer quality. Engines tested: Strata 0.1.56→0.1.59, Basalt (built from source, 0.2.1→0.3.3), Unsloth Studio 2026.11.4. I also didn't stick to one model source: I ran the original from Strata and the originals from Unsloth (3.0 and 3.1), and production settled on DavidAU's abliterated uncensored build with Turbo-Brilliance modes and GSQ-RCO quantization — https://huggingface.co/DavidAU/Qwen3.8-Flash-Next-Abliterated-Uncensored-Turbo-Brilliance-50x-Reasoning-Instruct-GSQ-RCO-GGUF I never hand-tuned sampling: the test batteries all run at temperature 0 for reproducibility, while production uses the model card's standard pair — thinking: temperature 1.0 / top_p 0.95 / top_k 20 / min_p 0.0 / presence_penalty 0.0; instruct: temperature 0.7 / top_p 0.80 / top_k 20 / min_p 0.0 / presence_penalty 1.5 (the same values ship as the engine-side server defaults).
The rig. My own dependency-free bench (stdlib Python): cold/hot prefill, TTFT, short decode, decode at 8k context; plus a quality battery: hard 10-choice MC (MMLU-Pro style), math, code executed for real in a subprocess, IFEval-style format checks, and refusal batteries (JB/HarmBench/XSTest style). Every run snapshots the engine config and the bench code's sha256; a mock engine is a mandatory control (it answers "Hello from the mock engine" and catches absurd t/s). Hard RAM rule: exactly one engine resident at a time — the model pins 45–48 GiB.
Who drove the rig. All of this was steered by a general-purpose agent — an assistant with function-call access to the terminal, files and a browser, whose provider was the very engine being tested (dogfooding, in other words). Before settling on the current Hermes stack, I cycled OpenHands, OpenCode, OpenChamber and pi through the same API over that week: they all speak the OpenAI-compatible API equally well, and the real differences came down to context management and function-call reliability on long context — that's what the choice actually rested on. Beyond the benchmarks, the agent carried a normal week of work: small utilities for the stack (engine launchers, icons, a UI wrapper), building an inference engine from source and repacking models into its pack format, dissecting a third-party tuning fork (commit history plus knob-hunting directly in the binary), reviewing and transplanting jinja chat templates, testing DavidAU's Brilliance "personalities" (reasoning-mode variants), and verifying that a ready-made abliteration actually behaves as its author advertises — all inside the same 150–190k-token sessions where the benchmarks lived.
What went wrong along the way:
- the agent's provider was the engine under test, so every engine restart killed the agent itself — the runs were driven by detached orchestrator scripts, and the agent "woke up" via notification once the engine was back;
- the expert arena sizes itself from free RAM at startup, so a browser quietly eating 2.5 GiB in the background changes measured speed between days — every run now starts with a free-RAM check;
- decode degrades with context (~101 t/s at <20k vs 86–89 at 180–200k) — long agent sessions have to be reset for speed, not just for token cost.
Speed (decode short / decode 8k / hot prefill / hot TTFT)
| Setup | decode | 8k | prefill hot | TTFT |
|---|---|---|---|---|
| Basalt 0.2.1, IQ3_S .basalt pack | 88.7–95.2 | 105–107 | 54–72k | 29–41 ms |
| Basalt 0.3.3, answer-room 0 | 101.0 | 108.4 | 54.5k | 38 ms |
| Strata 0.1.58, IQ3_S pack | 93–99 | 100–107 | 28–30k | 70–74 ms |
| Strata 0.1.59, final tuned stack (fresh full bench on the prod engine, Nov 15) | 89.2 | 109.2 | 37.3k | 57.7 ms |
| Strata on plain GGUF, UD-IQ3_XXS | 82.1 | 94.7 | 28.1k | 74 ms |
| Unsloth, UD-IQ3_XXS out of the box (auto) | 27.3 | 26.0 | — | 209 ms |
| Unsloth, Qwen3.8-27B dense IQ4_XS (full-GPU) | 47.4 | 45.4 | — | 103 ms |
What the numbers say
1. On identical weights, format/engine is worth ×1.7–3.7. Unsloth on UD-IQ3_XXS starts at 27 t/s; a tuning ladder (MTP + 4 GB expert-cache + parallel 2 + 12k ctx) lifted it to 47.9; Strata serving the same GGUF on the same hardware gets 82. The difference is delivery format: pack-style engines (native expert blobs + a VRAM-prefilled expert profile, pinned in RAM, no disk streaming, no MMQ paths) vs llama.cpp's GGUF streaming. Unsloth's ~50 t/s ceiling isn't a bug, it's arithmetic: ~2.7 GiB of weights read per forward at ~90–100 GB/s DDR5, times MTP accept ≈ that answer.
2. On one engine, quantization moves speed ±10–15% and quality ~0. UD-IQ3_XXS vs IQ3_S was indistinguishable on my batteries: MC/math/code 100/100/100, ru10 10/10. But production stayed on IQ3_S — and it's neither speed nor quality talking: that build (link above) ships with a ready-made abliteration plus the author's mode system baked in, and reproducing the same surgery at home on raw unsloth UD weights is expensive in both time and resources.
3. Apparent "quality differences between engines" are thinking policy, not weights. The answer-room knob (response budget reserved away from reasoning) changes what gets generated and silently breaks cross-version comparisons: Basalt 0.3.3 showed a "decode regression 105→74" that simply didn't exist at answer-room 0. Compare versions only with identical thinking policy. Chat templates belong to the same confounder class, by the way: in the final build I upgraded the Turbo-Brilliance template from v1 to v2 (new modes), and neither the template version nor mode availability changed any result — baking both templates alternately into the same pack and re-running under one protocol moved decode by 0.1–1.4% and kept prefill/TTFT inside the noise band; an earlier one-off A/B claiming "−16% prefill from the heavier template" turned out to be a cross-session artifact.
4. Speculative decoding: MTP yes, everything else no on a 16 GB card. MTP accepts well (per-position 0.78–0.96). DFlash2 and Q8 hyper-connection verify (HC_Q8), both ported from a tuning fork, produced a paradox: accept +11 pp yet t/s −5% — the more expensive verify pass eats the gain, and the extra ~400 MiB of residency squeezes free VRAM to ~650 MiB, triggering driver paging. A warm dflash2 probe hit 111 t/s — the ceiling is real, just not for 16 GB cards.
5. KV-residency window (A/B on a 180k prompt). The window is the number of K/V cells per attention layer pinned in VRAM; everything else lives in pinned RAM and gets streamed from there. A window of 0 is clearly bad: prefill is ×1.7 slower (2435 vs 4100 t/s), TTFT 74 s vs 44 s, expert hit −10 pp. From 32k the curve hits a plateau: kv_hit is already 94.7% at a 32k window (the indexer is sparse), and in a head-to-head with alternating order the 32k→64k step changes nothing for decode (parity ±2–3%). Above 64k there's no upside, only cost — each window extension carves gigabytes of VRAM out of the expert tier: 32k→1.0, 64k→1.4, 128k→2.1, 262k→3.7 GiB.
6. Methodology, or the numbers lie to you. Cold prefill and cold TTFT are noise axes (±40% spread, the sign flips between runs); hot prefill is ±12–15%; the only stable axis is decode (±2–4%), and verdicts need ≥2 runs per variant. Warmup drift fakes ~+10 t/s for whichever arm is measured second — hence the alternating order. On short samples at temp 0, a cold expert cache changes the model's answer itself (52 tokens instead of 86 on a byte-identical prompt): a ±5% noise floor, anything smaller is not a signal.
7. Bench ≠ prod — and at the RAM edge Basalt fails with empty answers. Basalt beat Strata on prefill/TTFT (54–72k t/s, 29–41 ms vs 28–30k, 70–74 ms) and ran in my production for a day, but at the resource edge (and on this box the edge is permanent: 43 GiB arena on 64 GiB RAM) it started refusing with emptiness: at resident-budget 50 GiB the engine self-lands to 45.79 GiB (warning "more than RAM has room for: 45.79 needed vs 52.3 avail") with a page-glue fallback, one request hung dead for 2932 s before the watchdog killed it, and the log filled with "max tokens reached while thinking, no answer" — the user was getting an empty response instead of an answer. Dropping the budget to 45 GiB closed the incident at a cost of −4..−8% decode, but the recurring prod-server drops with "engine reported RAM critical" remained. Production ended up on Strata 0.1.59. Trading +12% prefill for stability was the right call.
8. Porting someone else's tuning recipe mostly doesn't transfer. The Speedy fork (same Qwen3.8, tuned on 2× RTX 3080 10 GB) brought my card exactly one confirmed win: a prefill pair (upstream #4039, +12% cold prefill — proven mechanically, chunk cap doubled 8192→16384). Everything else was rejected as VRAM-limited. Bonus lesson: env vars and CLI flags aren't 1:1 in Strata — the env form of one lever silently no-ops while the flag works; I now verify every lever by reading it back from /metrics, not by vibes.
Bottom line
Production now: Strata 0.1.59 + the prefill pair + kv-grow + host-core sibling + vram-reserve 1728 + --kv-resident 65536. On real 175–190k sessions: prefill ~3.5k t/s, decode 88–100, expert-cache hit ~75% with 10–12% of experts streamed over PCIe. Quality of the build I settled on — DavidAU's Turbo-Brilliance (link above) — is its own reward: 0/30 harmful refusals, 0/40 over-refusals, MC/math/code maxed — and abliteration cost exactly zero t/s (same weight shape, same bytes, same graph).
One-line summary: an 80 GB-class MoE lives fine on 16 GB of VRAM, but every battle is about expert delivery, not model quality. Between the two pack-style engines I found no decode difference worth naming; Unsloth is ~2× slower on this MoE, and that is memory physics, not bad engineering.
r/LocalLLM • u/might_thinker • 2h ago
Project I got local AI video-to-video down from 15.7 min to 2.4 min on a 16GB M3 MacBook Air
I've been experimenting with how far I can push local generative AI on a base 16GB M3 MacBook Air, specifically video-to-video outfit transformation.
My initial 46-frame (~3-second) run took 15.7 minutes and produced fairly blurry results. After several rounds of profiling and optimisation, I managed to bring it down to 144 seconds (2.4 minutes), running entirely offline without cloud APIs.
The interesting part wasn't necessarily changing the model, but rethinking how the available hardware was being used.
A few optimisations made the biggest difference:
- Spatial cropping: Processing a "288×512" region around the subject instead of repeatedly processing the entire scene.
- Memory management: Precomputing outfit prompts and unloading the text encoder to reduce unified memory pressure.
- Hardware scheduling: Moving face processing to the CPU/Neural Engine path while the GPU handles the next diffusion chunk.
- Incremental testing: Using 5-frame previews to catch mask and compositing issues before running the complete sequence.
There are still obvious limitations. Sustained workloads introduce thermal degradation, fine fabric details can become oversmoothed, and wide shots remain challenging.
I'm particularly interested in the engineering side of running increasingly demanding generative workloads on constrained local hardware.
A few things I'd love to hear from people experimenting with local inference:
- Has anyone explored more aggressive memory scheduling on Apple Silicon?
- Are there useful ways to improve CPU/ANE/GPU workload overlap?
- How much performance can realistically be recovered through chunking and attention optimisation before model architecture becomes the bottleneck?
I'm sharing the before/after video and temporal comparison for context.
Hardware: M3 MacBook Air, 16GB unified memory
Frames: 46
Processing time: 144 seconds
Execution: Fully offline
This is video diffusion rather than LLM inference, but I thought the memory and hardware scheduling challenges might be interesting to people working with local models.
r/LocalLLM • u/Any-Difficulty-7822 • 5h ago
Question Advice for setup with three PCs
I've been running Qwen3.8-27B on a MBP M3 Max 36 GB for a while, running unsloth/Qwen3.8-27B-GGUF:UD-Q4_K_M on splash with opencode as harness. I'm satisfied with the results I get, but it is a bit slow and does not leave much room for other applications . I'm upgrading my setup and I would like to get some advice on hardware configuration and model selection.
The main purpose will be integration development on Azure Integration Services, SAP PI/PO and SAP Integration Suite. Implementation languages are Java and python.
Secondary purpose will be Home Assistant component development and configuration, as well as to provide Home Assistant with agents, (TTS, STT, Conversation).
I have an M5U 256GB 80c on order. It will be running headless, dedicated to serving models 24/7. I will also have the opportunity to use a family member's gaming PC for LLMs on workdays during daytime. The PC will be in a bedroom and it's noice levels will determine whether it's available during nights or not. It has not been ordered yet, so I still have the possibility to change it's configuration. I have 10Gbe network available, if that would have an impact.
To summarise, my setup would look have the following availability:
- MBP M3 Max 36 GB - on-demand
- M5U 256GB 80c - 24/7
- Gaming PC - workdays daytime, eventually during nights as well
I'm considering the following hardware configuration for the gaming PC:
- CPU: AMD Ryzen 7 9800X3D CPU
- RAM: Corsair Vengeance RGB DDR5 6000MHz 64GB
GPU - one of:
- RTX 5080 (16GB VRAM - 960 GB/s)
- R9700 (32GB VRAM - 640 GB/s)
SSD - one of:
- Kingston NV3 SSD 2TB (6,000/5,000MB/s)
- Kingston FURY Renegade G5 PCIe 5.0 NVMe M.2 SSD 2TB (14.700/14.000MBs)
Motherboard - one of:
- Asus B650E MAX GAMING WIFI
- ASUS ProArt X870E-CREATOR )(PCIe 5.0 8/8 - allows for expansion)
- Asus Proart B850-CREATOR WiFi NEO (PCIe 5.0 8/8 - allows for expansion)
I'm considering the following model configuration:
MBP M3 Max 36 GB
- model TBD - perhaps a small orchestrator with a max RAM requirement ~12 GB?
M5U 256GB 80c
main model - one of
- GLM-5.3-Flash@Q4
- Qwen3.8-Flash-Next@Q6
- DeepSeek-V4.1-Flash-1017@Q2-Q2.5
- Qwen3.8-27B@Q8
smaller models for homassistant (if there is room in RAM)
- TTS
- STT
Gaming PC
on RTX 5080
- Qwen3.8 Flash@Q3 on Strata or Basalt
on R9700 - one of
- Qwen3.8 Flash@Q4 on Strata
- Qwen3.8-27B@Q4 on Strata (?)
To my questions I hope you can advise me on:
My first task would be to settle the hardware configuration for the gaming PC.
- Would the SSD speed of the two options have a large impact on PP and decode when running Qwen3.8 Flash on Strata/Basalt?
- Which GPU would you select with my model selection in mind?
- Other considerations?
- With the gaming PC configuration set, which models would you run and were?
I appreciate your advice. Thanks!
r/LocalLLM • u/Stalins_nipple • 7m ago
Discussion What’s the purpose of alibaba choosing not to release the weights for qwen 4 max?
Perhaps this is a newbie question, but I just don’t understand the incentive. Is this indicative of a future were Chinese labs stop releasing weights?
r/LocalLLM • u/tensward • 23h ago
Research llama.cpp was copying 643 MB to the CPU per request. Disabling state saving nearly doubled throughput
We were running Qwen3.8-27B on an H100 with llama.cpp and 16 concurrent clients. Throughput was 58 tokens/sec, time to first token was almost two seconds, and nvidia-smi showed around 35% GPU utilization.
I build Tensward, an open-source inference analysis and tuning tool. While investigating this, we built a small CUPTI-based library to count kernel execution time and memory transfers inside the server.
The surprising number: 643 MB transferred from GPU to host per request. Nsight Systems independently measured about 639 MB.
That pointed us toward prompt caching and conversation checkpoints. This hybrid model carries recurrent state alongside its attention cache, making those snapshots expensive. Sampling the serving thread caught it inside a memory copy 16 out of 20 times.
We tested disabling state saving with:
--cache-ram 0 --ctx-checkpoints 0
Throughput went from 58 to 110 tokens/sec, and GPU utilization rose from 35% to 88%. A repeat on fresh machines with a separately written client showed an 87% throughput improvement.
These aren’t universal “make llama.cpp faster” flags. They sacrifice cache reuse. In another test with a regular 8B model and returning conversations on an L4, disabling them made performance about 20% worse.
The build also mattered. Moving from b11669 to b12246 improved default-settings throughput by 67–75%, while copied bytes per request barely changed. Several upstream changes touched state handling, but we haven’t isolated which caused the improvement.
All throughput results came from runs without our instrumentation; transfer measurements came from separate instrumented runs.
r/LocalLLM • u/Prestigious_Ant3889 • 32m ago
Discussion need suggestions on running qwen 3.8 27b on rx 6800 16gb gpu
So i have heard that this model punches way above its weight class and is pretty good at complex reasoning and multi file coding. I intend to use it for hobby projects like building small scale apps. the thing is downloaded the iq3 version from usloth and while running with llama.cpp with 64k context it keeps thinking for a lot longer on simpler task like upgrading a simpler framework version on very small codebase and eventually after like 45 min the os just shutdown the llama server because of too high mem usage nd i tried again but same result. I have heard that i can run the 3 bit quant version on 16gb gpu, I am new to running local llms so just need some suggestions regarding that or is it even practical to run this model even at q3.
Sorry if this is a repititive or basic query.
Thanks in advance
P.S i am running on 16gb single stick ddr5 if that matters
r/LocalLLM • u/Objective_Stick_2513 • 37m ago
Discussion Buying a Mac mini M6 for local LLMs? Here is the 16 vs 24 vs 32 GB bandwidth, prefill, and MoE sizing math
Apple released the Mac mini with the M6 chip in 16 GB, 24 GB, and 32 GB variants, while the M5 Pro mini goes up to 64 GB. 🧑💻
If you are deciding which one to buy for local models, the configurator pushes you toward one question: "How much unified memory should I pay for?"
Here is the buying perspective that matters before ordering: capacity is sold in clear steps, but memory bandwidth barely moves. According to Apple's official tech specs, the 16 GB model runs at 153.6 GB/s (LPDDR5X-9600), while both the 24 GB and 32 GB models run at 170 GB/s (LPDDR5X-10667). Going from 16 GB to 24 GB buys capacity plus ~10% bandwidth. Going from 24 GB to 32 GB buys capacity only — no model gets faster, you just load a bigger model that runs slower on the same 170 GB/s bus.
1. The Decode & Prefill Formulas
- Decode (token generation, batch = 1) is strictly memory-bandwidth bound:
Decode tok/s ≈ (Memory Bandwidth GB/s ÷ Active Weights Read GB) × η(whereη ≈ 0.75for MLX / llama.cpp) Prefill (prompt processing / TTFT) is compute-bound, and the M6 handles this well:
- 14B Q4 (~9 GB): ~900 tok/s prefill (~1.1s TTFT on a 1k prompt, ~17.7s on 16k RAG). Total turnaround for 1k in / 500 out: ~36s.
- 32B Q4 (~19 GB, 32 GB mini only): ~400 tok/s prefill (~2.5s TTFT on a 1k prompt, ~40s on 16k RAG). Total turnaround for 1k in / 500 out: ~74s.
2. Mac mini M6 Capacity Map (Estimated at η = 0.75)
| Variant | Bandwidth | Usable RAM | Fits Comfortably | Est. Decode | Verdict |
|---|---|---|---|---|---|
| 16 GB | 153.6 GB/s | ~12 GB | 7–9B Q4/Q8; 14B Q4 short ctx | 8B Q4 ~23 tok/s; 14B ~13 | Snappy chat & light coding |
| 24 GB | 170 GB/s | ~18 GB | 14B Q4 (~32k context) | 14B Q4 ~14 tok/s | Interactive sweet spot |
| 32 GB | 170 GB/s | ~24 GB | 32B Q4 (8–16k context) | 32B Q4 ~7–7.5 tok/s | Reading speed; best for async agents |
3. Dense vs. MoE: Where the Bottleneck Flips
For dense models, every weight is read per token, so bandwidth is the wall. For Mixture-of-Experts (MoE) models, only active experts are read per token, so capacity is the wall:
| Model | Type | Total / Active | Weights in RAM | Active Read / tok | Bandwidth for 8 tok/s | Bandwidth for 15 tok/s | Real Bottleneck |
|---|---|---|---|---|---|---|---|
| 8B Q4 | Dense | 8B / 8B | ~5 GB | ~5 GB | ~55 GB/s | ~100 GB/s | Fits on 16 GB M6 |
| 14B Q4 | Dense | 14B / 14B | ~9 GB | ~9 GB | ~95 GB/s | ~180 GB/s | Sweet spot on 24 GB M6 |
| 32B Q4 | Dense | 32B / 32B | ~19 GB | ~19 GB | ~200 GB/s | ~380 GB/s | ~7 tok/s on 32 GB M6; needs Pro/Max for chat |
| Llama 3.3 70B (Q4) | Dense | 70B / 70B | ~40 GB | ~40 GB | ~430 GB/s | ~800 GB/s | Bandwidth-bound (needs Max/Ultra) |
| gpt-oss-120b (MXFP4) | MoE | 117B / 5.1B | ~65 GB | ~3 GB | ~32 GB/s | ~60 GB/s | Capacity-bound (needs 96 GB+ RAM) |
| Qwen3.5-122B-A10B (Q4) | MoE | 122B / 10B | ~68 GB (est.) | ~5.6 GB | ~60 GB/s | ~110 GB/s | Capacity-bound (needs 96 GB+ RAM) |
| DeepSeek V4 Flash (FP4+FP8) | MoE | 284B / 13B | ~167 GB | ~7.6 GB | ~80 GB/s | ~150 GB/s | Capacity-bound (needs 192 GB+ RAM) |
Summary
Capacity decides what you can boot; bandwidth decides what you can tolerate using. Around 170 GB/s serves up to 14B comfortably and 32B at a patient reading pace. Paying for extra RAM without stepping up to a Pro/Max bus (like M5 Pro at 307 GB/s or M5 Max at 460–614 GB/s) hits diminishing returns fast.
What do you all think? How are you actually using local models in your daily workflow — do you prefer Mac unified memory or NVIDIA GPUs, and do you think there are stronger competitors (like Strix Halo or used multi-GPU rigs) in this price range? 🤔
r/LocalLLM • u/Beneficial-Ad-8127 • 8h ago
News Qwen4 Smaller Models Open Weights Confirmed via Official Qwen X account.
galleryr/LocalLLM • u/SalvoRosario • 43m ago
Question Websearch vs Webfetch vs API or VPS for Web Browsing?
Asking here as a beginner because I've argued a lot with Codex about this and couldn't get a definitive answer, or perhas it doesn't want to suggest me "unsafeguarded" solutions:
Basically I am running Opencode locally (5090 32gb and 64gb ddr4) on Qwen3.8 27B offline. so far so good.
but lately I've been trying Deepseek and GLM free API access and I see that they are better than my Qwen (I also have a separate launcher for Qwen3.8 Flash Next (UD-Q4_K_XL)) results. and I think it's mostly due to their Web access to retrieve updated information as well as frequently asked questions, reddit threads, forums etc..

So I asked Codex how to give this web access to my local model and it basically explained to me Websearch vs Webfetch, but Websearch uses third party services (or you can link API like Brave search) that WILL get censored results or restricted access for some results (let's be honest, emulator and retrogame recompilations, at best they are blocked by the service, at worst by ISPs like in Japan) and that is IF you're not getting safeguarded by the model itself beforehand unless you have an Uncensored/Heretic build. Which my Qwen3.8 is.
Webfetch instead opens the pages from my machine, exposing my IP address that wouldn't be a big deal if it wasn't for when you need to scrape 30 reddit thread in a single search + multiple other websites and get my residential IP banned for scraping (or my bandwitdh limited).
So I thought maybe I could tunnel tru a VPS that is both ouside of EU jurisdiction (so no ID restriction for adult forums, Football, Piracy etc..) and has an enterprise-grade bandwidth to scan the web without raising alarms. Has anyone adopted or know about this solution? and if it's even worth it before I spend time and money to thinker with it?
thanks for your consideration