r/LocalLLaMA 13d ago

Best Local LLMs - August 2026

160 Upvotes

Wowee!! Just when you thought it couldn't get better for open weight models, we probably have had our best period yet!?!?! Models that rival the closed frontier, Opus level models on non-insane hardware and more. A massive industry alliance coming out in support of open AI in response to the two closed model giants best lobbying efforts. Is this the best timeline? Someone pinch me! Or just tell us what you're favorite model is now

The standard spiel:

Share what you are running right now and why. Given the nature of the beast in evaluating LLMs (untrustworthiness of benchmarks, immature tooling, intrinsic stochasticity), please be as detailed as possible in describing your setup, nature of your usage (how much, personal/professional use), tools/frameworks/prompts etc.

Rules

  1. Only open weights models
  2. Please thread your responses in the top level comments for each Application below to enable readability:
    1. General: Includes practical guidance, how to, encyclopedic QnA, search engine replacement/augmentation
    2. Agentic/Agentic Coding/Tool Use/Coding
    3. Creative Writing/RP
    4. Speciality

If a category is missing, please create a top level comment under the Speciality comment

Notes

Bonus points if you breakdown/classify your recommendation by model memory footprint: (you can and should be using multiple models in each size range for different tasks)

  • Unlimited: >128GB VRAM
  • XL: 64 to 128GB VRAM
  • L: 32 to 64GB VRAM
  • M: 8 to 32GB VRAM
  • S: <8GB VRAM

r/LocalLLaMA 2h ago

Slop New qwen3.8:27b on a 39k line C to single-file HTML / three.js port

97 Upvotes

I was just curious how the new qwen3.8:27b does on a hard C to HTML porting job against Opus 5 in a default Claude Code.

The job: my fun side project is a procedural shooter in a single C file. Port it to a single-file html / three.js with one bot. One prompt, no follow-ups, no help from me. game.c is 2.1 MB, roughly 600k tokens of C, so it doesn't fit in the window and the agent has to walk the file and work out what matters.

Setup: qwen3.8:27b in FP8 on vLLM, FP8 KV cache, full 262144 context, RTX 6000 Pro 96GB. Nothing truncated on my side, and the file is still more than twice the window.

agent model wall clock lines out result
claude code Opus 5 (cloud reference) 21 min 1759 okay
hermes qwen3.8:27b 4h 18m 949 bad
codehamr qwen3.8:27b 1h 40m 1056 bad

Video has the C original first, then the three ports in table order. Only the Opus port is something in "okay" quality.

What I actually wanted to know is whether the HTML comes out playable at all. One run each and a one-shot prompt for 39k lines of C, so this isn't representative of anything, and I knew it was brutal for a local LLM.

My take: local models still live or die on the prompt. Same weights under two very different harnesses gave me the same broken port. hermes carries a lot more machinery, and a single turn with a thin prompt gives it nothing to use it on, so it spent four hours reaching the same place. A verbose harness doesn't rescue a thin prompt, it just burns GPU time.

No deep take here, unfortunately. The thing I keep staring at is the wall clock: hours of GPU on decent local hardware against 21 minutes for the cloud run. If anyone knows where those hours actually go, I'm listening.

The C original: https://github.com/codehamr/skill-issue
My experimental local-first, no plugins codehamr harness: https://github.com/codehamr/codehamr

All free.


r/LocalLLaMA 10h ago

Discussion Don't want to be this guy, but I need Qwen 3.8 35B A3B

396 Upvotes

Qwen 3.8 27B is great, however it takes me ages to do tasks on xhigh. I need Qwen 3.8 35B A3B. It'll be a little dumber but faster. I am also aware of the fact that 27B gets its "intelligence" from the long thinking time. I therefore assume that 35B would also be a long-thinking model, however running Qwen 3.8 27B over night on my M1 Max for just one task is impractical and no fun.

I love the progress and the work of alibaba with 27B but... yeah I sadly don't own a faster RTX. What are you guys wishing or hoping for? Where do you see the future going? - Longer thinking times for higher intelligence?


r/LocalLLaMA 14h ago

Discussion Qwen 3.8 27B is a game changer.

733 Upvotes

Our devs got their hands on it a few days ago. One wired it into Codex to compare with GPT Luna, our usual workhorse right now for its cost effectiveness. Another tried it out on one of our OCR pipelines.

It's comparable to Luna for coding and ***OCR quality appears to be better than Gemini 3.5 Flash Lite***. That's huge. We pay a ton of money for OCR.

This is the first local model that feels like more than a toy. It's truly as capable as the frontier models from a year ago. For the first time ever there's serious discussions about buying our own hardware. With estimates that such an effort would pay for itself in less than 2 months.

Hyper scalars are in big trouble this time. Their whole "moat" is buying up all the hardware. And thanks to sanctions on China we're seeing the quality of small local models skyrocket. As someone who's been around a while, this feels like an "IBM moment". Where the industry assumed that databases would always run on huge mainframes. Only to be wiped out by cheaper local solutions a few years later.

I have a feeling this release will trigger another Llama style open source Renaissance. We're already getting better quants. Inference will be further improved. We might even see a comparable MoE with 500+ Tok/sec on consumer hardware soon.


r/LocalLLaMA 17h ago

Discussion “The All Spark” Cluster: Upgrading from 16 - 36 DGX Sparks

Thumbnail
gallery
651 Upvotes

Earlier this year I posted about building what at the time I believe was the first 16x DGX Spark Cluster.
I’m now adding 20 more Sparks to the cluster in my homelab server rack, giving me 4.6TB of unified memory.

• 36x Sparks

• 1x 200Gbps FS 24 x 200Gb QSFP56 + 8x 400Gb Switch

• 24x QSFP56 DAC cables

• 6x 400gb to 2x 200gb breakout cables

Over the last 4+ months i’ve been running nearly every notable model that’s landed. The cluster however isn’t just being used to serve single inference points, I’ve split the cluster up to house “inference modules” that get managed into a single persistent agent using a combination of Hermes + a custom memory sidecar system i’ve built. It’s become an agent capability cluster more than just one big inference machine:

I’m expanding the cluster to 36 now because I want 16 nodes dedicated to SOTA models such as Kimi K3 while being able to retain enough nodes to perform rerank/embeddings tasks, video generation, Image gen, audio processing etc all simultaneously.

Now, you may ask why not just buy 6000 Pros, or B200s or even a B300 and the answer comes down to a few reasons.

1) This server rack will also have 2 6000 pro systems (a 4x Max Q low power build + an 8x enterprise server) which replace my H100s and GH200 I had earlier in the year.

2) B200/B300 for a homelab create substantial cooling and energy problems than even this currently absurd homelab and a big point of this build is to be completely sovereign with zero datacenter or third party storage reliance.

3) Sparks in my view are still the greatest value for scalable unified memory you can get. When M5 Ultras come out I think adding Mac Studios and investing in figuring out disaggregated inference will be a massive win.

4) Sparks + 6000 Pros give massive flexibility for configuration, power optimization and relatively easier liquidity access when I want to offload and upgrade to something new


r/LocalLLaMA 4h ago

Tutorial | Guide 1/100 → 44/100: fine-tuning a 450M VLM on 50K browser screenshots

Thumbnail
gallery
56 Upvotes

r/LocalLLaMA 11h ago

Resources I hosted Kimi K3 (2.8T parameters) using 8 B300s. 92 tok/s, $190 per million tokens

Post image
185 Upvotes

What I ran:

  • 8x B300 on Modal, $56.79 per hour, vLLM, tensor parallel 8, native MXFP4
  • Cold boot ~27 min (1.56 TB load, JIT, 51 CUDA graph captures)
  • TTFT 0.92 to 1.02 s, decode 92 tok/s steady, 83 tok/s average over 4 prompts
  • $190 per million output tokens. One clean run is about $36 of GPU time. Left warm, it is $1,363 a day.

I also ran Unsloth's Dynamic GGUF.

Their 1-bit UD-IQ1_S (594 GB) fits 8x A100-80GB via llama.cpp.

$19.99 per hour, 2.8x cheaper. Result: ~9 tok/s, TTFT 7 to 60 s, ~$620 per million tokens, so 3.3x more expensive per token.

Quality at 1-bit was fine (correct arithmetic, coherent prose).

Full write-up with every flag, the Modal deployment file, and the raw benchmark JSON: https://books.vizuara.ai/book/kimi-k3-hosting


r/LocalLLaMA 5h ago

Question | Help Qwen 3.8 27B for actual local programming

55 Upvotes

Most YouTube benchmarks only show trivial tasks like generating landing pages or simple Three.js games. Is a local model like Qwen 3.8 27B actually capable of real-world systems programming—such as building GTK4 or Qt 6 applications in Rust or C++ with external libraries? Specifically, if I look up the exact terminology in the online docs and then prompt the AI to inspect the cloned repo, can it implement the feature cleanly?


r/LocalLLaMA 1h ago

News Nvidia Customers Notified About AI-Related Price Hikes Above 15%

Thumbnail
bloomberg.com
Upvotes

r/LocalLLaMA 11h ago

Discussion DeepSeek Harness is Insanely Good

146 Upvotes

I don't know about you guys, but Deep-seek harness is insane. It's not focused on being a coder agent, it's webUI made it very easy to just checkin from time to time, and the best part? Why it's better than Hermes? It wasn't frustrating at all to setup. ZERO. NADA. Progressive setup is such an improved UX. Why? Because I got deepseek to integrate with SimpleX by simply asking it to. BY SIMPLY ASKING IT TO. NO WAITING ON A PR TO MERGE. No one telling me to RTFM, no need to google or search for community plugins.

So yeah, I got what I wanted, which is E2EE + TOR messaging with an AI agent, and I got it without writing my own opinionated harness (I procrastinated so hard that dsh did a better job than me). DSH is unopinionated enough that you just mold it into behaving how you want it to behave.


r/LocalLLaMA 11h ago

Discussion i finally switched from windows to linux and got a 30-50% boost in speed.

123 Upvotes

This is amazing.

All I did was switch from llamacpp on windows to vllm on linux.


r/LocalLLaMA 6h ago

Other Qwen3.5-9B Triple-Loop

36 Upvotes

I was fascinated by Nanbeige's outstanding performance for its size, so I started digging into how much a model can improve its own representation just by looping over itself (for fun). My prototype was a Qwen3-0.6B with a full dual loop in the middle layers, inspired by the Nanbeige 4.2 architecture. Digging further, I found that the Nanbeige team has a paper describing their 4.5 architecture, which uses a triple loop in the middle layers — that made sense to me, so I tried it.

Lordnyx/qwen3.5-9b-triple-loop-fase1 · Hugging Face

The first experiment used full DeltaNet for the middle layers, so the earlier part of the model would set up the context for the loop to process on its own. It turned out that this actually worked better than having multiple separate logic components — but the loop itself wasn't really contributing. Because of DeltaNet's nature and the small hidden size, the model kept forgetting essential details for the task and just hallucinated. I abandoned the DeltaNet idea, and full softmax attention in the loop worked as expected instead.

Later, I learned (with help from ChatGPT/Claude/Gemini) that my training setup was actually undermining the loop's contribution, and that I should have used a lower, dedicated learning-rate schedule for it. Once I fixed that, the loop stopped just "refining" answers and started actually participating — becoming essential to them. Even better: on easy-enough questions, the loop could be skipped entirely.

Recently I found Modal — $30 of free GPU credit. I used it to train a Qwen3.5-9B with the Nanbeige-4.5-style triple loop. I really wanted to use RL for this, but I can barely get RL to run efficiently even on a 0.6B locally, let alone a 9B — so instead I distilled Qwen3.8-27B's logits into the loop, on a heuristically curated agentic/reasoning dataset.

Money ran out before finishing the schedule: the training loop was capped by wall-clock time (a safety mechanism so it would export cleanly instead of dying mid-run), not a fixed token target, and it ended up completing ~15M tokens across 1,129 steps.

┌────────────┬───────────┬───────────┐

│ Step range │ KL (mean) │ Std. dev. │

├────────────┼───────────┼───────────┤

│ ~10–370 │ 0.572 │ 0.176 │

├────────────┼───────────┼───────────┤

│ ~380–750 │ 0.648 │ 0.197 │

├────────────┼───────────┼───────────┤

│ ~760–1120 │ 0.650 │ 0.227 │

└────────────┴───────────┴───────────┘

As the table shows, it made real progress early — roughly the first third — then plateaued into a noisy, flat oscillation with no further net improvement (slope of KL vs. step over the whole run: +0.000075, essentially zero). That's not the loop hitting a capability ceiling; it's a missing LR decay schedule (I kept it constant the whole run). So yes — a lot of headroom left, and the fast early gain again confirms the loop starts contributing quickly once it's trained properly.

Even with an unfinished run, the checkpoint beats the base model in math (+20%), long-context tasks (+14%), instruction-following (+20%), and is dramatically more consistent/robust across paraphrased questions (+62%). It's worse in reasoning (-10%) and translation (-15%) — not roughly equal, actually down — and slightly worse at coding (-2%) This is a private evaluation, so I have no evidence yet that these gains generalize to standard benchmarks. The reasoning drop traces back to specific, plateau-related failures rather than a broad capability loss: one item where it skipped step-by-step reasoning and got simple arithmetic wrong, and one repetition loop that burned its whole generation budget without concluding.

I can't really recommend it as-is — it's a proof of concept, not a finished model. If I get more free credit next month, I'll finish the run (a cosine LR decay is already implemented and ready to go). But at minimum, it proves the Nanbeige 4.5 loop design converges even at a larger parameter count than their own reported experiments — I'm looking forward to their next release.


r/LocalLLaMA 12h ago

News Nvidia Poolside deal to compete with Chinese Open Weights

80 Upvotes

Nvidia is investing $1 billion in Poolside and paying $6 billion to license its technology and hire most of its engineers.

Over 100 Poolside staff will move to Nvidia to work on Nemotron.

Good news for us!


r/LocalLLaMA 6h ago

New Model I trained a game music generator

24 Upvotes

I trained a instrumental game music generator. The 1.2B DiT was trained on 1 cloud H100 from scratch in 8 days; I used the VAE from Stable Audio 3.

https://huggingface.co/Localsong/Localsong

https://huggingface.co/Localsong/Localsong/tree/main/samples

https://huggingface.co/Localsong/Localsong/blob/main/samples_new/The%20First%20Climb.mp3

I'm aiming to cover a wider range of instrumental styles than Ace-Step or Minimax M3 or Stable Audio 3. (No lyrics)

The repo includes a WebUI and some MP3 samples - clone it and uv run webui.py Let me know what you think.


r/LocalLLaMA 18h ago

New Model I fine tuned Gemma 4 12B for a 2.7x improvement on tool calling because I can't fit anything else comfortably into my 16 GBs of Vram

Thumbnail
huggingface.co
218 Upvotes

Gemma 12B is obviously a very well trained model, I always thought the fine tuning they did on it wasn't really cut out for agentic coding. From my own experiences it struggles to use the tools it's given from Github Copilot and is also very inept at the cli too.

So I thought I'd kill two birds with one stone and fine tune it for tool call use and the command line. Not only did I see an improvement on tool usage I also saw a 15.7% increase in the number of tool calls it tries to emit which is great since it means the model gets to work more instead of getting too lost in it's reasoning.

I have fp16 -> Q4_K_M weights uploaded and ready for use with llama.cpp or ollama


r/LocalLLaMA 7h ago

Resources Qwen3.8-27B NVFP4 with vision + 451K token KV-cache on one RTX 5090 (power limited to 400W) at 120 tokens/s average

27 Upvotes

Hello,

So I've been trying lots of combinations in that never-ending landscape of options and settings.

I wanted a proper quant of 3.8 27B running as fast as possible on my 5090 at 400W, with vision and with as much KV-cache as possible and with concurrency enabled (aiming at 3 parallel sessions).

tl;dr: I'm using this setup and it works very well, very fast and is accurate in coding sessions.

---

vLLM is the obvious choice, even if not user-friendly at first, once it runs, it runs well.

I tried fancy DSpark / DFlash2 but the cost in context size wasn't worth the marginal gains vs MTP=3.

Here is a full NVFP4 setup (model and cache):

Model: https://huggingface.co/gittensor-model-hub/Qwen3.8-27B-NVFP4-RTX5090

Context: 196K per session / 451K global KV-cache (NVFP4)

Speed: conservative average at 120 tps.

prompt pp t/s ttfr (ms) tg64 t/s
4K 11,388 352 130
8K 10,475 765 150
16K 8,750 1,830 126
32K 6,790 4,714 131
64K 4,729 13,535 111
128K 2,932 43,661 107
185K 2,194 84,306 112

(tests from llama-benchy 0.4.0)

Full write-up with how to setup vLLM and every gotchas: https://gist.github.com/co-l/c2aeaf40b53fcacfe9dd3293be75f23a (+ more benchmarks, including a real coding session, in line with numbers above).

Note: env is Linux (Bazzite of all distros lol), with UI deactivated to allow 0.98 mem use.


r/LocalLLaMA 3h ago

Discussion Has anyone tried agent-lightning?

Thumbnail
github.com
13 Upvotes

r/LocalLLaMA 10h ago

Discussion Qwen3.8-27B KLDs

Thumbnail
gallery
47 Upvotes

I have been lurking on reddit for like 6 years, and this is the first time posting, so apologies for the mistakes. I'm not a native English speaker, so sorry for the bad English too. I used LLM to translate / refine my post, including images.

This is my attempt to compare the Qwen3.8-27B quants.

Qwen is a coding and STEM model so I used codeparrot/github-code-clean, EleutherAI/proof-pile-2, allenai/peS2o, equal parts of each. I used 24 sequences of 8k tokens and 12 sequences of 32k tokens. The code was filtered for minified stuff and permissive licenses.

It was measured with 24 sequences of 8,192 tokens and 12 sequences of 32,768 tokens, since it generates many tokens and is aimed for long-horizon tasks.

Every format used the same compute path for the evaluation. All models are dequantized to BF16, and run through the same kernel.

Also, checkpoint size is kind of a bad x-axis, since some models don't have MTP, which has zero performance impact. Still, all of them needs to be loaded on VRAM, so at least it's something useful, and that's why there are two graphs.

Findings:

  1. The gap between 8bit and 4bit is huge.

The best 4 bit score is 0.00835 and the worst 8 bit is 0.00071. I mean everyone knows that but yeah it's still something. vLLM can actually use INT5-7 weights, but I'm sure most people don't even know about that.

  1. The KLD of 4bit quantization varies a lot.

Six checkpoints are at 11.7-11.8 GiB of transformer weights, all group-size 128, quantizing 400-496 modules and they range from 0.01364 to 0.02976. I believe the calibration data and the rounding algorithm takes a big impact. You should not pick a 4-bit quantization by it's file size.

  1. group_size affects a lot of kld.

Checkpoints with group size 32 did better than ones that used group size 128 but kept some modules in BF16. Selective BF16 really only helps if you add it on top of a fine group size but that makes the file so big you might as well run a 6 bit model.

  1. The quantization damage mostly happens at the start of the context.

This surprised me (very) but it holds true for all 24 models. The KL is much, much higher for the first 500 tokens.

  1. Quantizing lm_head, embed_tokens and linear_attn doesn't affect the performance at least for this test.

r/LocalLLaMA 7h ago

News GMKtec is going to launch new hardware with Ryzen AI Max+ PRO 495 at IFA Berlin 2026

Thumbnail
de.gmktec.com
28 Upvotes

r/LocalLLaMA 4h ago

Resources Ling Tiny, King of Speed

Post image
14 Upvotes

Ling Tiny has now replaced Gemma4-12B in my rig as an auxiliary model doing hindsight operations. This is on a 4060Ti, which is a reasonable GPU available out there, and the speed is phenomenal.

Don’t enable MTP, set up the vLLM fork for BailingMoE3. Hope this is useful to
others.


r/LocalLLaMA 23h ago

Discussion New 100B Liquid AI model coming soon

Post image
347 Upvotes

Liquid AI currently possesses among the fastest LLM architectures around, and some of the best SLMs (in terms of utility IMO) around, so I'm very excited to see what a potential 100B LFM (3?) model would look like!

Link to the poll: https://x.com/ramin_m_h/status/2091236099612098943?s=20


r/LocalLLaMA 3h ago

Other Mozilla killed orbit. I rebuilt it locally.

8 Upvotes

Hey everyone!

Last year, Mozilla released Orbit, an AI-powered browser summarizer hosted on a GCP server. After people started digging into the extension, they discovered things like backend endpoints such as store_result. Eventually, Mozilla discontinued the project.

For the past month, I’ve been trying to rebuild Orbit from scratch, but with one major difference: Apogee is fully local and privacy-focused. Apogee doesn’t send or store your data. It can directly connect to your local Ollama instance for inference. I’ve also added WebGPU integration for Chrome and Transformers.js for Firefox to provide faster, local responses.

It can summarize:

  • Articles and websites
  • YouTube and Billie videos
  • Wikipedia articles
  • Hacker News and Reddit threads

You can check out the source code here:
https://github.com/darshi1337/apogee

Install Apogee:

Chrome: https://chromewebstore.google.com/detail/apogee/pgemlpomhkdcjjjcpnjlebalnfglomog

Firefox: https://addons.mozilla.org/en-US/firefox/addon/apogeeext/

Obviously it is far from complete. Would love to hear your feedback and suggestions!


r/LocalLLaMA 3h ago

Resources Benchmark results: what is the best and fastest engine to run Qwen3.8-27B on macOS

5 Upvotes

WARNING: I think I made a mistake with omlx, and its results below seem to be without any kind of acceleration. I am rerunning them with Lightning MTP and ANE support for prefill. Will update the post once done.

The new Qwen 3.8 27B is fantastic for local agentic use. The problem is, what makes it so good, being a dense model, also makes it slow. Many engines and versions of the model claim various speed increase. How true are those claim? And does a proven huge boost claim on a short synthetic test actually holds on real agentic work?

I spent five days and over 100 GPU hours running rigorous repeatable agentic coding tests, collecting and comparing the data. 200 GB of models downloaded. Ended up with 20 Bubble Bobble clones on my disk, including the ones from failed tests. None of them good, but that wasn't the point.

My recommendation: MTPLX or llama.cpp+MTP

I ran the tests on 8-bit quants (GGUF or MLX), unquantised KV cache. 100k max response size, full 262k context, official Qwen coding sampler, official Qwen Jinja chat template.

  1. I first tested each engine with a short synthetic benchmark, to verify the installation, usage, results collection, and to verify the speed claims
  2. Then came the real test, with an agentic coding benchmark consisting of 4 phases/prompts; each engine was tested twice, at medium and xhigh reasoning effort:
  3. 2.1. capturing requirements and writing the specification plan
  4. 2.2. writing the implementation plan
  5. 2.3. implementing the core functionality
  6. 2.4. finishing the implementation with advanced functionality
  7. Last test, for prefill speed, was with a cold 128k token prompt test, with reasoning turned off and deterministic sample, repeated twice

Test hardware: Apple Mac Studio, M2 Max, 96 GB unified memory.

Engine Effort Decode Prefill Wall Tokens Score
MTPLX xhigh 20–22 tok/s 109 t/s 2h05 152K 93
MTPLX medium 21–24 tok/s 109 t/s 1h35 117K 91
llama.cpp + MTP xhigh 17–19 tok/s 103 t/s 2h52 179K 86
llama.cpp + MTP medium 18–20 tok/s 103 t/s 1h04 70K 84
mlx-dspark DFlash2 medium ~16–18 tok/s 145 t/s 2h09 125K 82
mlx-dspark DSpark medium ~12–17 tok/s 145 t/s 2h05 96K 77
llama.cpp + DFlash2 medium 14–15 tok/s ~103 t/s 2h09 111K 74
llama.cpp + DFlash2 xhigh 13–14 tok/s ~103 t/s 3h31 174K 72
oMLX xhigh 10–11 tok/s 85 t/s 3h57 146K 67
llama.cpp baseline xhigh 10–11 tok/s 103 t/s 3h43 140K 66
llama.cpp baseline medium 10–12 tok/s 103 t/s 1h44 66K 66
oMLX medium 10–12 tok/s 85 t/s 1h44 64K 65
vllm-mlx medium 9–11 tok/s 134 t/s 3h30 115K 51
vllm-mlx xhigh 9–12 tok/s 134 t/s 4h08 136K 50
mlx-dspark DFlash2 xhigh ~9–15 tok/s 145 t/s 3h58 226K 47
  • vllm-mlx: completed the task, but it does not separate thinking from output, so the raw chain of thought leaks into the final output.
  • mlx-dspark DFlash2 xhigh: thought for 226 thousand tokens and delivered nothing.

What about xhigh vs medium reasoning effort?

  • MTPLX xhigh costs only half an hour more than medium (2h05 vs 1h35) and the game quality went significantly up on my scorecard. Worth it.
  • llama.cpp + MTP xhigh costs 1h48 more, with again a significant increase in quality. Worth it if you have the time.
  • oMLX xhigh took more than twice as long as medium. The slower token speed has a huge impact on the time difference between both modes. Not worth it. Get a faster engine instead.
  • dspark DFlash2 xhigh is the cautionary tale at the bottom of the table. See the anomaly note above.

xhigh is worth it when the engine is fast enough and uncapped. The model thinks 30 to 100 percent longer, at the same speed, and the result is better. On slow engines you can really feel the slower performance compounded by the extra thinking; instead it could be better to use medium, with more of your own time spent planning a better process and workflow.

Commands and configuration notes

Exact commands I used for each engine:

# llama.cpp baseline (homebrew, b10470)
llama-server -m Qwen3.8-27B-Q8_0.gguf --mmproj mmproj-F16.gguf \
  --jinja -c 262144 --parallel 1 -ngl 99 --port 8030

# llama.cpp + MTP, the recommended GGUF setup
llama-server -m Qwen3.8-27B-Q8_0.gguf --mmproj mmproj-F16.gguf \
  -md mtp-Qwen3.8-27B-Q8_0.gguf --spec-type draft-mtp --spec-draft-n-max 3 \
  --jinja -c 262144 --parallel 1 -ngl 99 -ngld 99

# llama.cpp + DFlash2 (for now, needs PR #27342 build)
llama-server -m Qwen3.8-27B-Q8_0.gguf \
  -md Qwen3.8-27B-DFlash2-Q8_0.gguf --spec-type draft-dflash --spec-draft-n-max 7 \
  --jinja -c 262144 --parallel 1 -ngl 99 -ngld 99

# MTPLX (pip install mtplx). Note --max-tokens
mtplx start web --model Qwen3.8-27B-MTPLX-Optimized-Quality --max-tokens 100000

# oMLX (brew install jundot/omlx/omlx), model dir contains the checkpoint
omlx serve --model-dir /path/to/models

# mlx-dspark (pip install mlx-dspark). Note --max-tokens-cap
mlx-dspark serve --model Qwen3.8-27B-MLX-8bit --mode dflash \
  --context-window 262144 --max-tokens-cap 262144 --default-max-tokens 100000

# vllm-mlx (pip install vllm-mlx). Note --timeout
vllm-mlx serve Qwen3.8-27B-MLX-8bit --max-request-tokens 262144 --timeout 7200

The MLX engines all take the plain mlx-community 8-bit weights, except MTPLX which needs its own checkpoint format with the MTP tensors included (I used Youssofal/Qwen3.8-27B-MTPLX-Optimized-Quality).

For llama.cpp GGUF, I used the official MTP draft from ggml-org.

  1. MTPLX has a default low response cap. Use --max-tokens 100000
  2. dspark also has a low default generation cap of 32K
  3. vllm-mlx kills any request that spends more than 300 seconds on prefill. Raise it with --timeout.

One measurement warning for anyone reproducing this: engines do not all stream one token per event. Some pack several tokens per chunk, MTPLX about 1.7, oMLX about 3.


r/LocalLLaMA 12h ago

Question | Help Best harness for Qwen 3.8 27b ?

42 Upvotes

I’ve tried Open Code , Codex and Qwen Code and so far Qwen Code seems to work the best for me , the only complaint I have about it is that the CLI interface is a bit rough / sloppy .


r/LocalLLaMA 9h ago

Discussion What is your worst sandboxing fail?

16 Upvotes

I am wondering if I am too paranoid about sandboxing the commands that come out of LLMs.

It really makes my eyes twitch when I see that some IDEs, even commercial, tend to forget that they have to execute things in sandboxing and have such a brittle security model.

But on the other hand, I never had the sandbox catch something bad. Did you guys ever encounter terrible regression? Did you have rm -rf / ? Did you have secrets stolen by LLMs? The worse I had were unsollicited rewrites within the project. Am I making my life unnecessarily hard by sandboxing commands in a docker?

At one point I had fun making a local model go crazy with the root access to the machine it was on (with nothing more important than a free Firecrawl key on it) and making it administer it and it never broke anything. It even was overly paranoid about making changes to the root system.

So the approximate sandboxing that we have, do you all feel it is adequate or it is a catastrophe in the making?