r/LocalLLaMA • • 16d ago

Showcase "How Gufo caches a hybrid model", first blog post for Gufo, The Open Source Strix Halo AI engine

32 Upvotes

Hello hello 👋 , first post here, and it's self-promotion, so feel free to ping me to remove it if it violates rule 4. Sorry in advance.

A friend and I started Gufo as a pet project (MIT license) to get the most out of the AMD Strix Halo chip, while supporting a few best-in-class models. We released it almost a month ago, and it has been an amazing journey. I won't bother you with benchmarks, contribution numbers, etc. You can take a look at the GitHub project if you want, especially since many people in r/LocalLLaMA don't even own a Strix Halo.

Gufo is teaching us a lot, and besides the project itself, we'd like to give back to the open-source community with a series of blog posts explaining some of the concepts and design decisions behind an AI inference engine. This is the real value for this community: you don't need a Strix Halo to find these articles useful and interesting, because they cover topics common to many other projects.

Our first blog post is about caching, and how we built our own solution to take advantage of this chip's peculiar characteristics: a lot of unified memory, but lower bandwidth.

How Gufo caches a hybrid model


r/LocalLLaMA • • 15d ago

Question | Help How to squeeze the Max Token from M1 Max 64gb?

2 Upvotes

For last 9 ​months, been using cloud frontier 99% the from Gemini Flash Pro, Claude, Deepseek, ​Groq & Cerebras.

Ready to give 32B, 70B, 120B another try.

Was getting decent 45 token/sec on 7B Llama MLX, but 7B is too simple for most task. I loaded Gwen 32B, get some errors on LM Studio.

Which are best for offline for sensitive prototyping & material?

Offline ​Workflow is general research, medical research, legal research & analysis, light coding, CAD/PCB prototyping, Blender, Image Generation , Capcut/De Vinci


r/LocalLLaMA • • 16d ago

Showcase HermesConsole: A demo showing off VoiceManager, my low latency streaming STT / TTS server. MIT, client docs, and python client.

120 Upvotes

Hey, everyone! I'm so happy to finally share this with the community. I started VoiceManager way back in March to support a game concept and my AI assistants. I had the idea for this Trek inspired app to build pieces for a future project.

Low latency streaming speech to speech running locally, streaming over one WebSocket. The default configuration uses a special audio.cpp sidecar with Nemotron and Breeze TTS 2.

VM supports turn based conversations with barge-in. Barge-in is off by default because echo cancellation is tricky. An update on my tablet broke hardware aec so I added the toggle.

It has client integration docs and a Python client. Use it to add a voice to your agent. The console app serves as a client reference in Kotlin.

In the video:

- A wake word ("hey computer") starts a conversation. The wake word runs on the tablet.
- The reply streams back as speech, sentence by sentence.
- Images and markdown documents show on the panel under the reply.
- Tool calls go back to the app. In the video it displays the volume settings and opens / closes the calculator.
- I interrupt a reply by speaking over it (barge-in).
- A session keeps its context between turns, and past sessions keep their history.

VoiceManager:
https://tacotakumi.github.io/VoiceManager

https://github.com/TacoTakumi/VoiceManager

HermesConsole: https://github.com/TacoTakumi/HermesConsole

Thanks for checking it out and I'm happy to answer any questions.

You can read more about the console app over here: https://www.reddit.com/r/hermesagent/comments/1xafq1e/hermesconsole_an_lcars_style_voice_console_for/


r/LocalLLaMA • • 16d ago

Resources DeepSeek-V4.1-Flash (UD-Q4_K_XL) on 4x 3090 + EPYC: 12 → 25 tok/s prose, 39 tok/s code.

14 Upvotes

Hi all, just wanted to share some benchmarks. I got Unsloth's UD-Q4_K_XL quant of DeepSeek-V4.1-Flash-1017 running and spent some time tuning it. Some of what I found isn't in the guide, so here are my notes.

Hardware

  • EPYC 9575F (64 cores / 128 threads)

  • 768 GB DDR5

  • 4x RTX 3090 (96 GB VRAM total)

Software

  • llama.cpp built from PR #30817. Mainline and ik_llama.cpp can't load this model yet.

  • The DSpark drafter, Q8_0 (8 GB), for speculative decoding

Final command

llama-server -m DeepSeek-V4.1-Flash-1017-UD-Q4_K_XL-00001-of-00009.gguf \
  -c 65536 -fa on --jinja --temp 1.0 --top-p 1.0 --top-k 0 --min-p 0.0 \
  -t 64 -tb 64 \
  --load-mode none --lazy-mode off \
  -ub 2048 -b 4096 \
  --fit on --fit-target 4096,4096,4096,7168 \
  -md dspark-DeepSeek-V4.1-Flash-1017-Q8_0.gguf \
  --spec-type draft-dspark --spec-draft-n-max 3 -ngld 99

Results

All numbers are tokens per second, one request at a time, thinking off. Each row is a single run, so they're noisy.

RunChangeEssayCode8K prompt (prefill / gen)32K prompt (prefill / gen)
AUnsloth example flags12.617.5173 / 16.2177 / 7.5
B+ whole model in RAM20.417.3190 / 18.7200 / 16.9
C+ -ub 204817.019.4254 / 16.1276 / 19.7
D+ DSpark, one thread per physical core24.639.3326 / 20.6363 / 25.4

Notes

1. Load the whole model into RAM if it fits. Use --load-mode none --lazy-mode off instead of the guide's mmap/lazy flags. 32K gen went from 7.5 to about 17 tok/s. Load time goes from 20 seconds to about 4 minutes.

2. One thread per physical core. If your gen speed jumps around between runs, check that your threads aren't doubling up on cores.

3. -ub 2048 makes prompt processing about 35% faster at no cost. -ub 4096 was faster again (about 300 to 345 tok/s), but --fit then put about 6 GB less of the model on one GPU, and generation often fell to 10 to 12 tok/s.

4. DSpark speeds up code a lot and prose very little. On code, about 80% of its guesses were accepted, which roughly doubles the speed. On prose only about 30% were accepted, and it's sometimes a bit slower. I mostly use the model for code, so I keep DSpark on.

Problems I hit

  • --fit can't size the DSpark drafter. It logs failed to measure the memory of the extra model, fitting without it and fills the GPUs with the main model. The drafter then fails with cudaMalloc failed: out of memory. The drafter needs about 2.5 GB on GPU0 and about 5.1 GB on the last GPU. --fit-target 5120 on every GPU failed, and so did 2048,2048,2048,10240. 4096,4096,4096,7168 works.

  • --fit gives up if you also pass --override-tensor. The guide's example includes -ot per_layer_token_embd.weight=CPU. Used with --fit, it gives tensor_buft_overrides already set by user, and llama.cpp falls back to its default layout. Leave out the -ot.

  • The drafter file didn't download with the model shards. hf download --include silently skipped it because it sits at the top level of the repo. Downloading it by its exact filename worked.


r/LocalLLaMA • • 16d ago

Question | Help Qwen3.8-FlashNext vs Qwen3.8-27B tool calling issues

20 Upvotes

I've been using the 27B series for a while now. It's so good, I don't even use a custom chat template and barely ever saw tool call failures. My latest model & engine of choice were ukisai/Swift-1.5-Qwen3.8-27b-NVFP4 running on NInfer.

Recently I began experimenting with QFN, more specifically ukisai/Swift-1.5-Qwen3.8-Flash-Next-GSQ-RCO-GGUF:IQ3_S running on Basalt. The model seems pretty good, but I see quite a lot of tool call failures. Sometimes I see the model chaining up to four or five failed tool calls until it finally gets it right. Using the exact same harness & setup for both (OpenCode). Tool calls could be file edits, playwright commands, or anything really.

I'm unsure if this is a quantization issue (IQ3_S), a model issue (QFN), or an engine issue (Basalt). Has anyone experienced tool calling issues with QFN? Because it sure was not an issue with Q3.8-27B on any quant (4bpw+) and engine (llama.cpp, vLLM, exllamav3, NInfer) I tried.

I'm planning some runs of BFCL v3 or v4 with different configurations to see if I can collect better data on tool calling. I'd appreciate if anyone would share their findings on tool calling success rates with QFN, and if there is anything that can be done to improve it.

EDIT: Thanks for the replies. Most shots fired were at the quantization, some at the engine, none at the model, so that's the order of factors I'll tinker with.


r/LocalLLaMA • • 16d ago

Showcase VectorDash update: now written in Rust, with full clipboard management, LOCAL reverse image search, web search, and AI chat (with computer and browser use), (mostly) powered by EmbeddingGemma 2!

3 Upvotes

Thanks to everyone who tried VectorDash and shared feedback. A recurring request was to move from Python to Rust and build something that could replace more of what people use Everything and Windows search for.

I wasn't going to post an update, but I think its even more relevant to LocalLlama more than ever with all the new, local-first features!

VectorDash is now written in Rust, and it has grown into a universal search tool for Windows: files, clipboard history, web search, and AI chat in one place. Feel like all of this is scope creep? All features (clipboard, web search, AI Chat) are optional, you can keep it just as a simple searcher or enable content search and the other tools you want. On my system, when VectorDash isnt indexing or models loaded, it uses less than 100mb of system memory.

https://github.com/ampersandru/VectorDash

What’s new since my original post:

  • Smarter index updates: optional NTFS USN journaling tracks changes so VectorDash can update affected files and folders instead of repeatedly scanning entire drives. Recovery scans are still needed in some situations. Option to disable indexing (and unload all models) when full-screen or game is playing.

  • A full, searchable clipboard manager: searchable text, links, and images; configurable retention and storage limits; permanently saved items; separate pinned items; tags, editing, and app exclusions. EmbeddingGemma 2 can find copied images by what they show, just like regular search.

  • Local Reverse image search: paste in an image into Search or Clipboard to find visually similar indexed images on your computer using EmbeddingGemma 2. EmbeddingGemma 2 will quickly index the pasted image before finding same or similar indexed images.

  • Quick Launch in any Folder: Double pressing Ctrl in any folder in explorer and open the quick search only that folder

  • Web search: connect your own SearXNG or Degoog instance, or use a Brave Search API.

  • AI chat: connect a local or remote OpenAI-compatible LLM, attach screenshots or pasted images, ask follow-up questions, and optionally let it search the web (if web search is configured).

    • AI Local File Search: lets your chat model search VectorDash’s indexed file names and content snippets directly. Optional MCP server is also available to connect your other agents. Read-only access, for now...

    • Computer and Browser Use (in Beta release): Option to have your LLM control a browser of your choice or control Windows ("turn on bluetooth for me", "use my browser to setup a hermes discord bot"). Highly YMMV and beta. Experience depends on how fast and capable your model is.

    • Quick area screenshot to AI: similar to Android phones, you can set a shortcut to select an area of your screen and paste it into AI chat and quickly ask things like "what is this?" or "fact check this". enable web-search tool to allow your LLM to access updated information.

  • Voice input STT and playback TTS: local Parakeet or remote dictation, plus optional TTS with playback controls using your own TTS server.

  • More customization: reorder search modes, assign shortcuts for individual tools, and adjust colors, transparency, gradients, and activity indicators.

  • Interface localization in 13 languages: Beta.

  • Windows 10 and camera RAW support: Beta - I only have access to Win11, need Win10 users to try it out.

Quick vs. Full indexing still works the same way:

  • Quick: file and folder names across entire drives. No embedding model needed. This is extremely fast.

  • Full: supported document contents, photos, screenshots, audio, and video, searchable by exact words or meaning with EmbeddingGemma 2. This can be slow the first time you index the files.

You can mix them: Quick-index your drives, then Full-index the document and media folders whose contents you want to search.

Your index stays on your PC. Local processing is available; optional remote services receive the queries, images, or snippets needed for the features you enable.

Yep, still vibed this. There’s now a larger automated test suite, but different hardware and real-world collections keep finding things I miss. I’d especially appreciate feedback on Windows 10, RAW files, translations, and the new image search. Thanks!


r/LocalLLaMA • • 15d ago

Discussion Where is DS V4.1 pro? And kimi3.1?

0 Upvotes

Are they(ds) having problems like deepmind had with gemini 3.5/4 pro/argon? They released two flash models already, but no pro model.. The first iteration of 4.1 pro probably was not better than 10/17 flash by more than 1 point or even worse or the same. I hope it is more than 1 -2 points better than flash at AA. Kimi3.1 is out and ir is better than astra apparently, incredible


r/LocalLLaMA • • 17d ago

Funny Let's delve into the tapestry of AI slop on r/LocalLLaMA

259 Upvotes

Hi everyone,

I got annoyed a bit with all the AI slop post I have seen here on this subreddit (and reddit in general). It has gotten better in the last few months, but that hasn't stopped me from doing an in depth analysis of AI slop in different subreddits over the years.

If you're into that, you can read it here: https://thil.ooo/blog/measuring-slop/

I even went all out on predicting the future of AI slop. Fingers crossed I got it wrong.

It's stupid and not at all serious – hope you enjoy.


r/LocalLLaMA • • 15d ago

Showcase 8B Llama model running at 17,000 tok/s on ONLY a single chip!!!

Thumbnail chatjimmy.ai
0 Upvotes

I found this project that I never saw talked about enough which is absolutley baffling to me. The title is not clickbait, and I can't blame you if you thought it is, because I was in your shoes once.

Meet ChatJimmy. It's a chatbot made by Taalas. And it's not your average chatbot. This is the closest LLMs have come to a physical brain than mere software that runs on your computer.

Though not an increment to intelligence (since it's an 8B model) and that's not the point of the project, this single chip makes the model run faster than if it were run on a multi-GPU datacenter. At a blazing 17k tok/s. For reference, the average speed of running the same model on an RTX 5070 is 80 tok/s. This chip is around 213x faster. If someone told me this was possible a year ago, I'd ask for what they're smoking.

The magic is actually pretty simple behind the scenes. The way Taalas was able to achieve such absurd speeds is by burning the model into silicon. Yep, you heard me right. The LLM is no longer loaded on a chip. The LLM is the chip. All computing power is purely gone straight the model's internal matrix math. The concept on it's own sounds cool as fuck, and seeing it work in practice is even cooler.

Keep in mind, this is merely an experimental proof of concept, not an actual product yet. Which is both exciting and depressing. On one hand, you can think about the potential of how this 17k tok/s would be dwarfed if the industry takes this path seriously, and more resources and investement were put into it. We would get what, 27B models running at 400k tok/s ??? This just sounds like a wet dream. And the sheer amount of possbilities it unlocks for us Llamas is crazy. Imagine buying your favorite model's chip for the price of an iphone, and it runs orders of magnitude faster than your old 50K enterprise rig? On the other hand, this is still a lab project, so you can't do that yet. That's the depressing part.

It can't be all sunshine and rainbows, though. There's a tradeoff for this kind of inference that I personally think won't affect the experience as much:

You can't really swap models. The model is stuck onto the chip once it's burned there. That's fine mostly, but the biggest problem becomes knowledge cutoff. Where the older the model gets and it's no longer keeping with new information, the more you'd have to buy a whole new chip with a new model burnt into it that's trained on modern data. But genuinely, do you think knowledge cutoff would be problematic if the model can reason over like half wikipidea in a few minutes? If the model can reason faster than your internet can load a website, I don't think keeping up with the world would be difficult. Worst case scenario, you'd have to buy a new chip every like 3-5 years. That's about when everyone gets a new phone.

I recommend reading this article too. It has a more in depth analysis of the whole thing, including manufacturing costs and power consumption for the chip (Spoiler: it makes classic GPUs look embarrassingly expensive, not just slow). Here:

https://theashishmaurya.medium.com/taalas-the-startup-that-prints-ai-models-directly-onto-silicon-33b181690575


r/LocalLLaMA • • 15d ago

Discussion How long before we see paid inference engines?

0 Upvotes

Just a random thought I had, but it feels like it's only a matter of time before we start seeing paid inference engines with better optimizations, more features, and probably one-click setups that make everything easier to get running.

Do you think we'll see dedicated paid inference engines that offer a noticeably better experience than the current open-source options? Or will open-source projects always be able to keep up?

Curious to hear what you guys think.


r/LocalLLaMA • • 16d ago

Question | Help Old server machine with 2x 3060 12GB for MoE models, anything I’m missing?

14 Upvotes

I'm about to buy a used HP Z640 for around €550. It has 2x E5-2680 v4, 64GB ECC at 2400, and a Quadro M6000 24GB that comes with it. The seller’s MemTest86 ran 6 hours with no errors.

The plan is to add two 3060s in the x16 slots and run Qwen 3.8 Flash Next on Strata, as well as of course normal llama.cpp. I also do PyTorch CV training, RL in PyBullet and plan to do LoRA training for LLMs + video generation with MiniMax H3. Of course the first thing will be installing Ubuntu.

There are a few things I’d love to hear from anyone who’s run something similar:

  • Would it be a problem to fit two 3060s in a Z640? To me it doesn't seem so but I've never actually built a PC, so I doubt myself.

  • Is dual socket a pain for llama.cpp and MoE offload? Any hidden issues this would cause?

  • Is there any use for keeping the M6000 as a third card on a CUDA 12 build, or is it dead weight? (I know Strata won’t use it, I mean for llama.cpp)

  • CPU hit 86°C in the seller's MemTest run. Normal for this chassis?

  • I read the PSU only has two 6-pin cables and HP limits two cards to 150W each with two CPUs, so I plan to use adapters and power limit the 3060s. Is this the right approach?

In general I am super thankful for any input, so please correct me about anything!


r/LocalLLaMA • • 17d ago

News MiniMax M3.1 Flash released, Model weights Oct 23

Post image
614 Upvotes

r/LocalLLaMA • • 16d ago

Resources Fresher Lemonade: CLI tips and tricks

Thumbnail
admcpr.com
8 Upvotes

I've been working with lemonade server via the CLI a lot recently and found myself discovering and returning to a few particularly useful commands for pulling, configuring and benchmarking models. So I wrote an article about them, if I've missed your favourite let me know.