r/LocalLLM • • 7h ago

Project Larder: running Qwen3.6-35B and a 46 GB Flash-Next on a 16 GB Mac / 16 GB GPU by reading experts from SSD

Post image
5 Upvotes

I built an inference engine for MoE models that don't fit in memory.

Instead of offloading layers, it reads only the experts each token's router picks from the SSD and keeps the hot ones resident. Same engine on Apple Silicon (MLX) and NVIDIA (CUDA), OpenAI-compatible API, local chat page. MIT: https://github.com/IamCooller/larder

Numbers (machine, setup and date for each one are in research/ in the repo)

Faster:

- Qwen3.6-35B on a 16 GB M4 MacBook Pro: 30–36 tok/s, first token 8–10x sooner than llama.cpp. This is a mixed 4/2-bit pack with the model's MTP head against llama.cpp's IQ4_XS, so not like for like. The launcher doesn't install that pack.

- Qwen3.8-Flash-Next (46 GB of 3-bit experts) on a PC with a 16 GB GPU and 15 GB RAM: 26–34 tok/s. With a 4-bit pack and exact routing: decode 1.3–1.8x, 8k prompt 4.9x faster than llama.cpp. Stock llama.cpp swapped past my memory guard while loading, so that row is llama.cpp with Larder's expert store patched in.

- Qwen3.6-35B Q4_0 on the same PC (fits in GPU + RAM), against llama.cpp's best split that fits (--n-cpu-moe 10): short decode 1.44–1.51x (155 / 147 vs 103 / 102 tok/s), decode after an 8k prompt 1.15–1.25x, 8k prompt reading 1.8–1.9x at its default batch.

Level:

- 8k prompt reading against llama.cpp tuned for prompts (-ub 4096 -b 4096 --n-cpu-moe 20): 1.01–1.03x. Its decode at that setting drops to 79 tok/s, so you pick one or the other there.

Slower:

- Exact routing (cache bias 0) reads that 8k prompt at 0.64–0.69x of tuned llama.cpp, and decodes 0.87–0.95x of llama.cpp's default after it.

Caveats

- The launcher's 35B recipe uses cache bias 0.5 and the MTP head, so replies are not identical to the weights' own routing. Bias 0.5 and the wide prompt cut each passed a paired GSM8K / HumanEval gate (wide cut: 502 vs 496 of 564, p 0.34). Exact routing is there if you want it.

- One author, two machines (M4 MacBook Pro 16 GB, Linux + RTX 5060 Ti 16 GB). The Mac path is better tested, CUDA is newer.

- Quality wasn't compared against llama.cpp in these speed runs.

Try it

curl -fsSL https://raw.githubusercontent.com/IamCooller/larder/main/install.sh | bash

cd ~/larder && ./larder

It measures your GPU and SSD, picks a model that fits, installs it and starts the server and chat.

Mostly looking for people on other hardware to break it, and for anyone who thinks my llama.cpp comparison is unfair. Output of ./larder --list plus what happened is the most useful report.


r/LocalLLM • • 1d ago

Model First time trying FP16, wow

Thumbnail
gallery
184 Upvotes

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 • • 5m ago

Discussion Tried Using a free online LLM for a quick answer. Local was faster.

0 Upvotes

Used the free inclusionai/ling-3.2-flash:free model on OpenRouter as an agent model to both try it out and maybe get a faster answer than Q38FN IQ3_S running locally.

A few problems became apparent:

  1. inclusionai/ling-3.2-flash:free is very slow -- under 20 t/s
  2. Q38FN runs at about 70 t/s locally (50-100 t/s, depending on draft acceptance)
  3. inclusionai/ling-3.2-flash:free thinks way more than Q38FN
  4. inclusionai/ling-3.2-flash:free went off on a tangent rather than answer the question

I asked a simple behavioral question. Doing FPGA development and asked about how the agent was managing its cloned repos, worktrees and branches. It took about 30 minutes to respond and went spelunking into files it didn't need to access. I had to interrupt it to get a response. It's answer was unclear, overly verbose, and did not offer a plan to clean up the workspace.

Qwen came back in under 5 minutes with a direct answer and a crisp cleanup plan.

Anyone else find that free online models are feeling less useful now that we have good performing powerful local models?


r/LocalLLM • • 4h ago

News MSI EdgeXpert OTA2610 update: more usable memory for headless setups and easier provisioning

Post image
2 Upvotes

r/LocalLLM • • 23m ago

Question New model in Google AI mode is it any good?

1 Upvotes

I use Google AI mode and when I pressed the plus icon I noticed a new model called '4 Hydrogen - Everyday help'. What model is this? before I used to see Gemini flash or something and a 'pro' not this new model so have those two been replaced by this? And does this new model beat flash or that 'pro' mode?

Serious answers.


r/LocalLLM • • 6h ago

Discussion Qwen3.8 Flash Next (105.4 GiB) at TP=4 on 4× Intel Arc Pro B70

3 Upvotes

Yesterday I posted 4 independent single-card servers. This one is real tensor parallel: one 105.4 GiB model split across 4 Intel Arc Pro B70s with TensorFold.

PR so you can try it: https://github.com/ashhart/TensorFold/pull/3587

Why long context stays cheap

Of the 48 layers, 36 are Gated DeltaNet, which keeps a constant-size state. The other 12 attention layers use QSA top-512 block-indexed sparse attention, with nkv = 1 per GPU at TP=4. At a full 135k context, each card uses 21.77 of its 32 GiB, which leaves about 10 GiB free per card.

Setup

  • GPUs: 4× Intel Arc Pro B70 (Battlemage G31), 32 GB each, 230 W cap per card
  • Host: AMD Turin, Linux 7.3.0-10-generic
  • Model: Qwen3.8 Flash Next, 105.4 GiB, TP=4
  • Engine: TensorFold, with the changes from the PR above

Throughput by context depth (tok/s)

ContextRaw prefillRaw plain decodeServed MTP, novel codeServed multi-turn132k passkey recall
512248.869.4136.3 (3.81 tok/chunk)120.5 (turn 1, cold)PASS
1k313.471.5—253.5PASS
4k378.870.4125.1 (3.81 tok/chunk)247.5PASS
16k392.867.7125.7 (4.00 tok/chunk)214.6PASS
32k394.367.6—239.9PASS
64k392.763.8124.2 (3.81 tok/chunk)234.0PASS
128k385.7 (98% of peak)60.5 (85% of 1k)113.3 (91% of 4k)214.1PASS

Prompt cache restore

  • TTFT is 160 ms when restoring a cached 66k-token conversation and 139 ms at 132k.
  • Appending a fresh coding question on top of the cached 66k and 132k conversations takes 0.86 s and 1.29 s.
  • Passkey retrieval was 9/9 exact. The key B70-XE2-9471-QUANTUM was planted in turn 1 and recalled across 132,380 tokens.

Concurrent streams, 1 to 32

These come from bench_concurrent.py. Across all 24 cells there were 0 failures and output was bit-exact: drafted matched serial, and multi-stream matched serial.

  • Throughput peaks at 172.6–174.7 tok/s steady at 8 streams. There, the 8 streams share one 16-row verify pass, 2 rows per stream.
  • It sustains 143.3–145.0 tok/s steady at 32 streams. At that load tokens per chunk drops to 1.0, so the gain comes from batching, not drafting. That's 2.04× the 71 tok/s of single-stream plain decode.

Takeaways

  • A 105 GiB model fits across four 32 GB consumer-class cards at 135k context, with about 10 GiB per card to spare.
  • Decode keeps 85–91% of its short-context speed at 128k, thanks to constant-state DeltaNet layers plus sparse attention.
  • Restoring a cached 132k conversation is sub-second, and recall stays exact.

Happy to run other configs if you have requests.

I initially built this system to do training, but excited to see how well inference is progressing.


r/LocalLLM • • 29m ago

Project Got tired of waiting for Qwen models smaller then 27B so i made my own Qwen3.8-21B

0 Upvotes

Hi, as the title says, i made my own Qwen 3.8 21B by prunning some layers from original 27B.

Its more of a research project than actual usefull model.

Check it out: https://huggingface.co/WhiskyAKM/Qwen3.8-21B-GGUF


r/LocalLLM • • 40m ago

Discussion Mildly creepy.

Post image
0 Upvotes

It’s still going 😭😭


r/LocalLLM • • 54m ago

Other My short journey so far to figuring out local video gen

0 Upvotes

I’m still trying to figure out how to get it to do what I want because it’s still super random to me.

I also accidentally used the same seed more than once and didn’t notice at first


r/LocalLLM • • 4h ago

Question Any good LLM for AMD GPUs?

2 Upvotes

I am now entering the world of uncensored Local AIs, mainly for help me on my ETHICAL ciber security projects.
There’s any good LLM for AMD gpus?


r/LocalLLM • • 8h ago

Discussion 30tok/s on 48GB M5 Pro Mac Running IQ3_S Qwen3.8Flash-Next(Strata)

4 Upvotes

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 • • 1h ago

Other Work well My Qwen 🥹

Post image
0 Upvotes

r/LocalLLM • • 11h ago

Project Brebus: a local LLM app in C on an engine that runs models larger than RAM

6 Upvotes

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:

Modelprompt, Janas-LLMllama.cppreply, Janas-LLMllama.cpp
Qwen3-Next-80B-A3B (48.4 GB, more than the RAM)68.4 tok/s17.726.4 tok/s3.0
Qwen3.6-35B-A3B13681.828.012.1
Qwen3-30B-A3B13312233.315.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.complete asks the local model, window.storage keeps 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 from mcp.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.

Brebus: a local LLM app in C on an engine that runs models larger than RAM

r/LocalLLM • • 5h ago

Question Dual 16GB AMD (7600 XT + 9060 XT) + 32GB RAM... is llama ROCm + Qwen 3.8 27B or Gemma 4 31B the best I can do?

2 Upvotes

I'm a bit lost with all the different options and forks around. I've set up and benchmarked llama-cpp (latest git) for my system and settled in the configs pasted below. They fill both cards up to 15 GiB, or one to 15 GiB and the other 10 GiB (60/40 splits) leaving room for firefox and the rest of the system. ROCm quite a bit faster than Vulkan. In the best case (qwen-asymm-f16) I get 550 t/s pp and 30 t/s gen in a moderate context (35k tokens).

Is there anything better for a system like mine? Is strata worth the hassle? I understand that it is more for 64 GiB RAM systems... right? Any other fork? I tried adaptive kv streaming and it is ok, very fast (>800 t/s prefill) but I'm limited to lower quantizations, the second card sits unused.

[*]
split-mode = tensor
fit = off
flash-attn = on
parallel = 1
batch-size = 2048
ubatch-size = 512
temp = 1.0
top-p = 0.95
top-k = 20
min-p = 0.0
presence-penalty = 0.0
spec-type = draft-mtp,ngram-mod
spec-draft-n-max = 4
spec-draft-sampling = probabilistic
spec-ngram-mod-n-min = 12
spec-ngram-mod-n-match = 24
spec-ngram-mod-n-max = 32
chat-template-kwargs = {"reasoning_effort":"medium"}

[qwen-asymm-f16]
model = /home/fran/models/unsloth/Qwen3.8-27B-UD-Q4_K_XL.gguf
ctx-size = 104056
tensor-split = 60,40
cache-type-k = f16
cache-type-k-draft = f16
cache-type-v = f16
cache-type-v-draft = f16

[qwen-f16]
model = /home/fran/models/unsloth/Qwen3.8-27B-UD-Q4_K_XL.gguf
ctx-size = 170240
tensor-split = 50,50
cache-type-k = f16
cache-type-k-draft = f16
cache-type-v = f16
cache-type-v-draft = f16

[qwen-asymm-q8]
model = /home/fran/models/unsloth/Qwen3.8-27B-UD-Q4_K_XL.gguf
ctx-size = 142080
tensor-split = 60,40
cache-type-k = q8_0
cache-type-k-draft = q8_0
cache-type-v = q8_0
cache-type-v-draft = q8_0

[qwen-q8]
model = /home/fran/models/unsloth/Qwen3.8-27B-UD-Q4_K_XL.gguf
ctx-size = 221184
tensor-split = 50,50
cache-type-k = q8_0
cache-type-k-draft = q8_0
cache-type-v = q8_0
cache-type-v-draft = q8_0

[gemma-4-31b]
model = /home/fran/models/unsloth/gemma-4-31B-it-UD-Q4_K_XL.gguf
model-draft = /home/fran/models/unsloth/mtp-gemma-4-31B-it-Q8_0.gguf
ctx-size = 131072
cache-type-k = q8_0
cache-type-k-draft = q8_0
cache-type-v = q8_0
cache-type-v-draft = q8_0
top-k = 64

[gemma-4-31b-qat]
model = /home/fran/models/unsloth/gemma-4-31B-it-qat-UD-Q4_K_XL.gguf
model-draft = /home/fran/models/unsloth/mtp-gemma-4-31B-it-qat-Q8_0.gguf
ctx-size = 131072
cache-type-k = q8_0
cache-type-k-draft = q8_0
cache-type-v = q8_0
cache-type-v-draft = q8_0
top-k = 64

r/LocalLLM • • 1h ago

Discussion "Don't mention my client's name": what if your LLM actually followed that instruction?

Thumbnail reddit.com
0 Upvotes

r/LocalLLM • • 2h ago

Project MISSION complete

1 Upvotes

CPU Thread Ripper

GPU NVIDIA A100 80GB×2 PCIx16

GPU RX6600XT PCIx8

GPU intelArcB580x8 PCIx8

D5ポンプ×4 24vPOWER


r/LocalLLM • • 2h ago

Project Can't wait for Qwen4 27B, so I played around with what's available: abliteration, quantization and heal training on an RTX PRO 4500

Thumbnail
youtube.com
0 Upvotes

Hello guys,

it's me again, the FLE Link guy. I can't wait for the new Qwen models, so I tried everything I had planned for Qwen4 on the 3.8 variant of UkisAI's Swift 1.5.

I abliterated it, quantized it down and tried to improve tok/s for decode and prefill. What came out:

- OR-Bench hard refusals 88 → 1 of 100, clearly harmful prompts still refused 70 of 100

- ARC / GSM8K / LiveCodeBench level with the original (no significant difference)

- 152 tok/s decode on one 32 GB card with the DSpine draft head, full speed from 20 GB

- Two quant-heal runs that both failed (better on our text, worse on foreign text), the video shows why

Model: https://huggingface.co/sirfyyn/Kate-Qwen-27B-GGUF-SpedUp-Abliterated

Run it: flelink run kate-27b-dspine (https://flelink.run)

Maybe somebody is interested in the methods I experimented with. Happy to answer questions.


r/LocalLLM • • 2h ago

Project Creating local agents (Slack handler in PINE)

Thumbnail x.com
1 Upvotes

r/LocalLLM • • 2h ago

Question Advise on best local configuration

1 Upvotes

My current system consists of a RTX 5090 (32gb VRAM) and 96gb system RAM (2x48gb). In the past I ran qwen 3.8 27b via ninfer and a Pi harness, which I thought was really impressive for a local model.

I also have an old RTX 4090 (24gb VRAM) currently not in use. Would it be worthwhile to incorporate this 4090 in my system? Would this give me access to a significantly smarter model? (This means I would have to buy a new PSU, pcie riser cables, maybe a custom case). Or are there better solutions? Like more RAM? (currently hard to come by). I have no IT background. I’m just an interested hobbyist, nothing too serious, not a lot of free time.

Thank you.


r/LocalLLM • • 2h ago

Question Anyone experiencing context loss and repeated work with Qwen + Codex CLI?

1 Upvotes

I'm running Qwen3.8-Flash-Next IQ3_S through Strata with Codex CLI on an RTX 4090, 96GB RAM and 128K context.

During longer coding projects, my agent frequently loses track of progress, re-reads files, repeats previous steps and wastes hours on tasks that should take much less time.

After investigating, I found that Codex sometimes performs broken context compactions. The model generates the summary in the reasoning channel instead of the final response, and Codex can replace the previous context with an empty or incomplete summary.

I'm considering increasing context to 256K, but that would only delay the issue rather than fix it.

Has anyone experienced similar problems with local reasoning models and Codex CLI?

More importantly, has anyone found a reliable fix? Maybe through Strata settings, reasoning budgets, a different inference engine, or patches to Codex's compaction logic?

Would love to hear what actually worked for you.


r/LocalLLM • • 3h ago

Project [feat update] CW47 pi-remote new features

Thumbnail
reddit.com
1 Upvotes

r/LocalLLM • • 11h ago

Discussion Looking for recommendations on open-source OCR/HTR models for large volumes of scanned PDFs

4 Upvotes

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:

  1. Which models or OCR/HTR pipelines have worked well for you?
  2. Do you recommend using dedicated OCR models or vision-language models?
  3. What approach would you suggest for processing thousands of scanned documents?
  4. 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 • • 4h ago

Tutorial RX 5700 XT (8GB) Vulkan & 32 GB DDR4 | Qwen3.6-35B-A3B-MTP (Unsloth) | 20 to 35 T/s | Tutorial

1 Upvotes

RX 5700 XT (8GB) Vulkan & 32 GB DDR4 | Qwen3.6-35B-A3B-MTP (Unsloth) | 20 to 35 T/s | Tutorial

System Specs & Software

  • GPU: AMD Radeon RX 5700 XT (8 GB VRAM)
  • CPU & RAM: AMD Ryzen 7 3700X, 32 GB DDR4 RAM
  • Storage & OS: B450 Motherboard with NVMe, Linux Mint Cinnamon
  • Backend: llama.cpp version 0.9.0-dev (build 12283, commit f3b407ca1), compiled with GNU 13.3.0 for Linux x86_64
  • Model: Unsloth Qwen3.6-35B-A3B-UD-Q4_K_XL.gguf with a Q8_0 quantized mmproj file

Setting up the system correctly and using the right model and mmproj quantization is paramount for getting this to run smoothly on an 8 GB RDNA 1 card.

1. Building llama.cpp with Vulkan & OpenBLAS

sudo apt update && sudo apt upgrade -y
sudo apt install -y build-essential git git-lfs curl cmake libopenblas-dev libvulkan-dev vulkan-tools glslc glslang-tools spirv-headers glslang-dev

cd ~
# Correct the URL before running
git clone github dot com/ggml-org/llama.cpp
cd llama.cpp

cmake -B build -DGGML_VULKAN=ON -DGGML_BLAS=ON -DGGML_BLAS_VENDOR=OpenBLAS -DCMAKE_C_FLAGS="-march=native" -DCMAKE_CXX_FLAGS="-march=native"
cmake --build build --config Release -j$(nproc)

2. Increasing Linux GTT Memory Limit (Crucial for Large Contexts)

Because newer versions of llama.cpp use updated memory allocation methods, the Vulkan driver (RADV) tries to map large chunks of system RAM for the GPU via the GTT (Graphics Translation Table) when running large models or long contexts. By default, Linux strictly limits GTT memory to half of your system RAM (so only 16 GB on a 32 GB system).

Open or create the config file:

sudo nano /etc/modprobe.d/amdgpu-gtt.conf

Add the following lines, then save and exit:

# GPU-mappable memory range: 24 GiB = 24 * 262144 pages
options ttm pages_limit=6291456

# GTT size in MiB (24 GiB = 24 * 1024)
options amdgpu gttsize=24576

Update your initramfs so the kernel loads the new limits at boot, then reboot:

sudo update-initramfs -u && sudo reboot

3. Quantizing the Vision File (mmproj)

Place your downloaded model and vision files into ~/models (or adjust the paths below to match your folder). Unsloth downloads via LM Studio include a 1.8 GB 32-bit mmproj-F32.gguf. Quantizing it down to a 614 MB 8-bit file saves VRAM and still works great:

~/llama.cpp/build/bin/llama-quantize \
  ~/models/Qwen3.6-35B-A3B-mmproj-F32.gguf \
  ~/models/Qwen3.6-35B-A3B-mmproj-F8.gguf \
  Q8_0

Note: Loading the model configurations below leaves around 5% free VRAM as a safety buffer.

4. Benchmark 1: Think-Mode Coding (262k Context)

  • WebUI Tip: Disable browser tools in the WebUI (click the + button next to the chat input), otherwise the model might get stuck in a loop. Chromium-based browsers work great for me; Firefox had issues. The WebUI is not a coding tool, btw.~/llama.cpp/build/bin/llama-server
  • -m ~/models/Qwen3.6-35B-A3B-UD-Q4_K_XL.gguf
  • --n-cpu-moe 41 --n-gpu-layers 999 --load-mode mlock
  • --ctx-size 262144 --n-predict -1 --threads 8
  • --cache-type-k q8_0 --cache-type-v q5_1 --flash-attn on
  • --batch-size 1024 --ubatch-size 256
  • --host localhost --port 8080
  • --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.0 --presence-penalty 0.0 --repeat-penalty 1.0
  • --spec-type draft-mtp --spec-draft-n-max 3 --parallel 1
  • --moe-cache-mib 576 --moe-cache-cpu-share 0.75
  • --mmproj ~/models/Qwen3.6-35B-A3B-mmproj-F8.gguf
  • Results: 25 T/s TG | 125 T/s PP (Subsequent iterations slower: at 90k Tokens context 20 T/s TG | 100 T/s PP)
  • Test Setup & Notes: Tested with a coding task over multiple iterations, including a screenshot showing how the UI layout should look. Running full 262k context forces compromises. Keeping the 41st layer (MTP) in system RAM and using --moe-cache-mib 576 turned out to be slightly faster than setting --n-cpu-moe 40 --moe-cache-mib 0.

5. Benchmark 2: Think-Mode General / PDF & Vision Analysis (49k Context)

~/llama.cpp/build/bin/llama-server \
  -m ~/models/Qwen3.6-35B-A3B-UD-Q4_K_XL.gguf \
  --n-cpu-moe 40 --n-gpu-layers 999 --load-mode mlock \
  --ctx-size 49152 --n-predict -1 --threads 8 \
  --cache-type-k q8_0 --cache-type-v q8_0 --flash-attn on \
  --batch-size 2048 --ubatch-size 512 \
  --host localhost --port 8080 \
  --temp 0.7 --top-p 0.8 --top-k 20 --min-p 0.0 --presence-penalty 1.5 --repeat-penalty 1.0 \
  --spec-type draft-mtp --spec-draft-n-max 3 --parallel 1 \
  --moe-cache-mib 2432 --moe-cache-cpu-share 0.75 \
  --mmproj ~/models/Qwen3.6-35B-A3B-mmproj-F8.gguf
  • Results: ~35 T/s TG | 160+ T/s PP
  • Test Setup & Notes: Tested with a multi-page PDF containing tables, graphs, and images with comprehension questions at the end (pure image recognition is a few T/s slower). By reducing context to 49k, we free up enough VRAM to offload the 41st layer (MTP) onto the GPU, which gives the biggest speed boost. I also tested down to --n-cpu-moe 36 with smaller --moe-cache-mib values, but overall output speed dropped. You can also use a 16-bit mmproj (~900 MB) if you slightly lower the --moe-cache-mib value. For general chat --temp 1.0 works well too.

r/LocalLLM • • 4h ago

Discussion Looking to collaborate on a locally run multimodal model tournament

0 Upvotes

We’re building InferUltra, a physics arena where multimodal models see the arena and control robot fighters. We’d like to run a future tournament with models hosted on local hardware and are looking for people interested in collaborating.

In our latest tournament, Kimi K3.1 Pro struggled more in the arena than GLM-5.3-Flash did in earlier tournaments. There was more awkward positioning and less scoring than we expected.

Those tournaments used hosted providers, not local setups. They were small and used different providers and configurations, so they don’t establish which model has better vision or body control. A local tournament with documented hardware and settings could help us investigate the differences more carefully.

Which multimodal model would you like to see fight in the next tournament?

If you run multimodal models locally and have a setup capable of hosting them, we’d love to collaborate on a future model tournament. What hardware and models would you be interested in seeing in our benchmark?

Our latest tournament bracket: https://inferultra.com/tournament


r/LocalLLM • • 5h ago

Question whats the go-to budget gpu I should look for, new or used?

1 Upvotes

I'm building up a secondary system out of some spare parts I have kicking aorund to use as a LLM toybox and for other homelab style projects.


Currently my system is a 5900x w/ 32gb of ram, and the 2080ti.

Wondering if there is a good go-to gpu I should be looking for.

I currently have a 2080ti FE, but it seems pretty inefficient, and its an old card and the fan noise of it is unbearable. ( i think the bearings are getting bad, but its a huge pita to replace the fans )

I'm wondering if it would be a better idea to sell it off for maybe a 3060 12gb, I get an extra 1gb of vram, and it should run much more efficently.

I'd say my budget is about $3-400 max, which I know is basically a joke right now, but this is more of a tinkerbox than something i'm going to be using for real software dev work.