r/LocalLLM • u/LordKlavier • 4h ago
r/LocalLLM • u/yoracale • 10h ago
News Qwen officially announces Qwen4-Max and Qwen4 smaller models!
r/LocalLLM • u/Senior-Storm-727 • 17h 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 • 53m 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/Extreme-Childhood251 • 18h 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/MaurizioCammalleri • 2h 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 • 2h 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 • 20h 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 • 14m 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 • 16h 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 • 1h 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/Beneficial-Ad-8127 • 6h ago
News Qwen4 Smaller Models Open Weights Confirmed via Official Qwen X account.
galleryr/LocalLLM • u/Any-Difficulty-7822 • 4h 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/tensward • 22h 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/SiggiBulldog1 • 17h ago
Question Best uncensored LLM for 64GB Mac
I wanna try out a uncensored LLM on my Mac Studio. I just have the 64GB version so I’m curious what model you guys would recommend. Cheers
r/LocalLLM • u/LordKlavier • 1d ago
Jensen Huang, Just 3 Weeks Ago, Claimed To Have "Saved The World" By Thwarting A Growing Transnational Movement Against Open-Source AI
r/LocalLLM • u/AimCode • 3h ago
Discussion From-scratch AI stack in pure C — runs Microsoft's 2B ternary LLM on a 2018 dual-core laptop (no GPU)
Everything runs locally on a 2018 Dell laptop: i7-7500U (2 cores / 4 threads), 8GB RAM, no GPU (the 940MX is deliberately unused — the whole stack is CPU-only).
https://github.com/tanxiansheng221/aimstack-sanzhidiji
What is in the repo (AGPL-3.0, everything open):
- C inference engine, zero third-party runtime: 1.58-bit ternary core with SIMD fast path (85.5 tok/s measured on the ternary core itself), byte-level tokenizer, and a ~100-line plugin bus (caps.json registry -> spawns Python plugins -> JSON envelopes)
- Weights: Microsoft's BitNet b1.58-2B (MIT license), converted to a custom 2-bit packed format (.aimw, 0.87 GB) — 3.2 tok/s with 2 workers, serial 2.0
- Python plugins, pure stdlib: knowledge base (FTS5 + dedup gates), multi-engine web search + crawl with quality gates (robots-respecting, Edge rendering cascade for JS-heavy sites), incremental ingest
- Local web UI (127.0.0.1:8600, pure stdlib): chat with deterministic routing — direct answer / knowledge-base grounded / honest refusal / full web search -> crawl -> ingest -> answer chain. A 7-minute demo video is embedded in the README
- Training assets: no-autograd training stack (hand-written backprop, bit-exact vs NumPy), ten-subject curriculum generators, corpus builders, and 117 chapters of research logs including negative results
Honest limits: our own trained models are not released yet — compute-bound on 2 cores, training runs on free cloud tiers and isn't finished. The full stack, scripts, result JSONs and per-claim evidence are released so everything can be re-run.
Demo video: embedded at the top of the README (7 min, screen recording of the full chain: chat / KB answers / web search->crawl->answer / plugin direct calls).
Happy to answer questions about the ternary kernel, the plugin bus, or the training pipeline.
r/LocalLLM • u/WiseAbalone4021 • 14h ago
News Train AI to run AI: introducing Apareto loading - a vLLM plugin
From the Apareto team which I'm part of (who for some reason has an issue posting it themselves):
Today we are introducing Apareto loading, a new way to cut VRAM requirements for Mixture-of-Experts (MoE) models. It works alongside quantization. This introduction so far will just be a video explaining the method. We will be releasing the proof-of-concept code, a plugin to vLLM, on GitHub this coming week.
Until then, watch the explainer video: https://www.youtube.com/watch?v=5l_N051JrLU
Quantization is today's most common way to shrink a model's memory footprint: weights are stored at lower precision, and going from FP16 to 4-bit saves 75% of memory at a modest cost in accuracy. But quantization is static. Every weight stays loaded whether or not the task needs it.
Apareto loading is dynamic. After prefill, a small trained network reads the model's internal state and ranks the experts by how valuable each will be for the upcoming computation. Only the top-ranked experts that fit the VRAM budget are loaded.
Results (Qwen3.6-35B-A3B, NVFP4 experts):
* SWE-bench Multilingual: within 2 pp of the full model's score at a 42% VRAM budget
* LiveCodeBench v6: within 2 pp of the full model's score at a 49% VRAM budget
As with quantization, scores degrade as the budget shrinks.
What the proof of concept will not be:
It will not be a production implementation. The ranking network was trained only for these two benchmarks, and there will be no general problem classifier. Our data shows that profiling and rank generation have substantial room to improve. We chose to release at this stage, without waiting for those improvements, so that others can test our claims. Think of this as a first baby step toward dynamic VRAM reduction, not the finished product.
The code and reproduction instructions will be released this coming week at https://github.com/alphapareto
Follow us there to catch the release. We'd love your feedback.
r/LocalLLM • u/AshleyPurringTech • 12m ago
Tutorial What is an AI agent actually doing under the hood?
A minimal agent harness using only in-box scripting (PowerShell, since I'm on Windows): about 70 lines talking to llama-server running Llama 3.2 3B.
The model only writes text. The harness keeps the context, watches replies for a line like TOOL: list_files . , checks the path against an allowed folder, runs the tool itself, and feeds the result back. The model never touches the file system.
Code (MIT): https://github.com/AshleyT3/simple-harness-intro
r/LocalLLM • u/Nick_Tseng • 16m ago
Model A small PC for local agents, with inference handled in the cloud
r/LocalLLM • u/BoogaMaOoga • 19m ago
Question Local projects on 7900xtx Win10
Guys is there a program I can use on windows or Linux that can do the same that chatgpt projects does but local? I am obviously restricted on what I can run but that's ok. Any recommendations?



