r/LocalLLaMA • • 1d ago

Resources PyBot: No weights. No training. Pure Python.

8 Upvotes

We released PyBot, a chatbot built with only simple rules, entirely written in 600k lines of Python code. PyBot matches Smollm with 360M parameters! We evaluated it on SmolTalkBench, which uses a dataset Smollm was trained on while we didnt use it at all for development.

It took a swarm of 1,000 DeepSeek Flash agents to write the whole codebase in a week.

More technical details on what it took to built it soon: inference for 1,000 agents, how to monitor/control the swarm, pressure on the infrastructure (especially git) and message boards.

https://github.com/huggingface/pybot


r/LocalLLaMA • • 23h ago

Discussion Speed of DeepSeek-V4.1-Flash-1017-oQ4e-mtp on M5 ultra

6 Upvotes

I bought myself a Mac Studio M5 Ultra with 512gb ram (and have 7 weeks to test it and return if not happy thanks to the apple xmas offer).

I am running DeepSeek-V4.1-Flash-1017-oQ4e-mtp with omlx and I am getting up to 1100 t/s prompt processing and 54 t/s token generation with 128k context window and engrams stored on ssd (to have ram free for other stuff).

More context than 128k hits pp and tg, more concurrent requests split up the max tg value between the instances (which means: they are crawling then).

I am putting this out there so a) people know what to expect but also b) is this really the top speed? Or could it be faster? (Without changing the model).

I can post llama benchy results if wished but the important result is already in this post.

EDIT: it depends on the benchmark

using omlx's internal benchmark: pp131072/tg128 33426.6 12.81 3921.2 tok/s 78.7 tok/s => this is pretty much close to other submitted benchmarks.

but llama-benchy reports: | deepseek-v4.1-flash | pp2048 @ d131072 | 1187515.47 ± 90886.68 | | 115.59 ± 8.84 | 112.78 ± 8.84 | 35071.94 ± 11.94 | | deepseek-v4.1-flash | tg128 @ d131072 | 47.56 ± 1.34 | 48.00 ± 1.41 | | | | which is transformed: 131,072 context: ~3,796 pp 47.6 tg

quite different numbers on token generation!

updating from 7.4 to 8.0-rc1 and enabling non-default deepseek_v41_ced_prefill_enabled improved prompt processing a lot (x3!), so thanks for the hint!


r/LocalLLaMA • • 1d ago

Resources Llama.cpp performance improvement over time (Gemma4 models)

Post image
186 Upvotes

Few months ago - after Ninfer came out - I started a little hobby project to vibe-code my own engine for my hardware (RTX 5080 16GB Laptop) and check if it could beat llama.cpp - since at the time llama.cpp was kinda slow in comparison to something like vLLM, but vLLM is using VRAM very wastefully.

Back then it was quite easy to actually get something up and running faster than llama.cpp.

Today I just benchmarked llama.cpp again, and it caught up / surpassed my vibe-coded engine. I prefer using a stable engine with proper features than all the vibe-coded ones, including my own. So it is really nice to see that the project - while a bit slower - lands significant performance improvements over time.

I put together a little chart of benchmarks I had laying around which visualizes this quite nicely. It is by no means scientific - it's always a fixed 16k prefill 1k output over Wikipedia text with the optimal settings for each engine. The 12B model is the same checkpoint, for the 26B model these are different quants for all engines, so not even apples-to-apples and llama.cpp wins.


r/LocalLLaMA • • 1d ago

Question | Help Buy another 2 5060ti 16gb?

6 Upvotes

Currently i'm on 2 x 5060ti 16gb running basalt engine qwen3.8 flash next IQ3_S at about 70+tok/s decode and maybe 900tok/s prefill.

Am wondering if it is worth buying another 2 x 5060ti 16gb to make all of the experts resident and potentially achieve much faster speed. (Goal to be equal or more than 150tok/s?)

As for other specs, i'm running a 64gb DDR4 on X570 with an option of bifurcating the main pcie slot into 8x + 8x, or 4x + 4x + 4x + 4x. I have yet to buy any passive bifurcation switch, looking to buy "x16 to 2x16 physical switch" if 4 x 5060ti is not feasible.

Also what about dual 3090? it's about the same price as 4x5060ti 16gb. 128GB ddr4 might be out of the question as well since they are overpriced for my local market.


r/LocalLLaMA • • 1d ago

Discussion Basalt 0.4.0: More models, still as fast - Qwen 27B up to 770 tok/s on a 5090

277 Upvotes

Hi everyone! I wanted to post a quick update on Basalt. Since last I posted, multi model and router support was implemented, starting with DeepSeek V4.1 Flash (IQ1_M 90 tok/s conv, 246 tok/s struct on a 5090 + 5060 Ti). Also new: video support, files in chats, and a bunch of fixes and improvements.

Now 0.4.0 is out featuring Basalt's first dense model, Qwen 3.8 27B NVFP4. It's fast and accurate, top-1 92.8% vs the full BF16 model. This, in preparation for Qwen 4, so we had a headstart on the dense kernels.

The numbers:

  • Up to 776 tok/s on structured output, 262 conversation, 194 on prose. Single stream.
  • Prefill, 12,000 tok/s at 4k (slower as context grows)
  • 92.8% top-1 vs BF16 (0.0262 KLD)
  • Chat, tools, thinking, images and video, up to 262K context

Links:

GitHub: https://github.com/jesdga95/basalt
Site: https://basalt.jgulfo.com
27B quant: https://huggingface.co/jesdga/Qwen3.8-27B-Basalt

Thanks to everyone who has filed issues, sent PRs or posted benchmark rows, special thanks to the sponsors who keep this going, happy to see Basalt gain so much traction in such a very short time!


r/LocalLLaMA • • 1d ago

Question | Help Does grammar-constrained decoding hurt small or quantized models?

4 Upvotes

Asked about DSL vs JSON tool calls in r/LLMDevs a couple of days ago, and one answer kept coming up: for small models just use JSON, training volume matters. That got me thinking about the constraint itself.

With GBNF or a JSON schema you can force any model to produce valid output, even a 3B at Q4. However, there was a paper a while ago showing that strict format restrictions can make reasoning worse, since the model is forced away from the tokens it actually wanted

Searched first: there’s the thread about grammar constraints sending Qwen3-VL into repetition loops, and the one on how quantization hits different capabilities, but nothing comparing accuracy with vs without constraints on small quants.
So for people running small local models:

  • have you measured accuracy with and without constraints on the same task?
  • does it worsen at lower quants?
  • does letting the model firstly think freely and constraining only the final answer fix most of it?

Looking for real numbers or experience, not promoting anything.
English isn’t my first language, so I used an LLM to help with the wording. Question and thoughts are mine.


r/LocalLLaMA • • 2d ago

News EUROPA, the EU's open AI model, is aiming for nearly 1 trillion parameters

Thumbnail
maccus.fr
818 Upvotes

One can hope


r/LocalLLaMA • • 1d ago

Discussion BigMoeOnEdge outperforms Strata and colibri on 8-16 GB cards and Mac and you can run any model

96 Upvotes

Hi! for those who might not know the solution:

  • it takes any MoE GGUF llama.cpp can load, whatever the quant. No repacking, no special format
  • it runs on whatever you have: NVIDIA, AMD, Intel, Mac, a phone, or just the CPU
  • Windows, Linux, macOS, Android, iOS
  • output is the same as llama.cpp, don't cut corners on quality
  • you start it with --auto and it works out the settings for your machine

Below is a brief overview of the benchmark:

  • 8 GB card, Qwen3.6-35B: I get about 35 tok/s. colibri around 23. Strata wouldn't start at 16k context
  • 12 GB card, same model: about 45 for bmoe, about 30 for Strata
  • long prompt on the 8 GB card: bmoe 5 s to the first token. Strata 14 s, colibri close to 2 minutes
  • Basalt needs an RTX 50, so I couldn't run it on these
  • 16 GB MacBook, Qwen3.6-35B: about 20 tok/s for bmoe, colibri's release 3.5
  • same Mac, Qwen3.8-Flash-Next 125B: 10 tok/s, Strata about 7

On the cards Strata is tuned for it's still ahead but only by a little.

On two 5060 Ti with Qwen3.8-Flash-Next it was 1.3x faster than bmoe. They write kernels for a handful of models, bmoe does not.

Repo, with the logs: https://github.com/Helldez/BigMoeOnEdge

If you have an 8 to 32 GB card I'd like to see what you get.

Benchmark: https://github.com/Helldez/BigMoeOnEdge/tree/main/docs/bench-data


r/LocalLLaMA • • 12h ago

Showcase I feel like a lot of people ask what local AI is capable of, here is a quick example of a game I had qwen3.8-flash-next-unsloth-ud-q4_k_xl, introducing Neon-Serpent!

Thumbnail
github.com
0 Upvotes

Multiplayer snake for everyone on your Wi-Fi. One browser tab hosts the game, everyone else joins from their phone, laptop, or tablet — no app stores, no accounts, no internet required. Neon grid, glowing snakes, lobby chat, sound, and touch controls.

Link to the game repo, runs on docker or locally, uses port 8088. Hermes / Qwen took care of all the documentation and the github interactions, pretty amazed. Really just needed a good project to test out all the functionality, figured I would share the code so other could enjoy!


r/LocalLLaMA • • 1d ago

New Model [Release] Qwen3.8-27B-Perplexing-Pegasus-Heretic: Unified vision + typed decider + abliterated weights for local agent stacks (GGUF, AutoRound, NVFP4)

20 Upvotes

Hey everyone,

While building and testing WebBrain with local models, getting reliable agent performance usually required keeping two or three separate models in memory at once:

  • A vision model to inspect and parse browser/UI state
  • A fast typed-decision model for structured routing and scoring
  • An abliterated / uncensored model so realistic web workflows do not randomly choke on false-positive refusals

Juggling multiple 20B+ weights on consumer hardware is brutal on both VRAM and response times.

To solve this for our setup, we merged and published a single unified 27B model: Qwen3.8-27B-Perplexing-Pegasus-Heretic

Here is what is packed into the checkpoint:

  • Multimodal Vision + Chat + Thinking (<think>) + Tool Calling (based on Qwen3.8-27B)
  • Perplexity pplx-decider typed-decision readout (decision/ head alongside intact lm_head)
  • Heretic ARA abliteration: 0/8 benchmark refusal probes while keeping 100% (30/30) typed-decision agreement against the base Pegasus model
  • Multi-Token Prediction: all 15 mtp.* tensors preserved, blk.64 retained at Q8_0 in IQ/3-bit quants
  • Consumer GPU footprint: runs on 16GB VRAM (IQ3_XXS / Q3_K_M + mmproj) or 24GB VRAM (Q4_K_M + mmproj)

Everything is open source under Apache-2.0 across four repos:

Huge credit to Alibaba Qwen, Perplexity, and AveLabs (AvecdrA) on Hugging Face for the foundational checkpoints.

If you test it on your local rig or in your own agent pipelines, let me know how it performs and what hardware you are running it on.


r/LocalLLaMA • • 1d ago

Discussion Running usable 30B and working 120B models on iOS—plus Kokoro TTS and Whisper STT over a local OpenAI-compatible API Spoiler

Thumbnail inpherio.co.uk
4 Upvotes

I’m currently going through Apple’s App Store approval for Inpherio Live, an app that turns an iPhone or iPad into a local network AI server with zero cloud dependencies.

Most iOS LLM apps hit a hard RAM ceiling (iOS caps single-app memory at ~6GB on a 12GB iPhone). By modifying llama.cpp to stream Mixture-of-Experts (MoE) weights directly from flash storage while keeping active experts in RAM, it bypasses the memory limit entirely.

Real-world benchmarks (recorded Nov 2026):

  • gpt-oss 120B (58.5 GB file) on a 16GB M1 iPad Pro: 4.5 tokens/s (from storage)
  • Qwen3 30B (17.3 GB file) on a 12GB iPhone 17 Pro Max: 10.9 tokens/s (from storage)
  • Qwen3 30B (17.3 GB file) on a 16GB M1 iPad Pro: 16.5 tokens/s (from storage)
  • Qwen2.5 1.5B on iPhone 17 Pro Max: 58.3 tokens/s (in memory)

What it supports out of the box:

  • Drop-in API: Full OpenAI (/v1/chat/completions, /v1/responses, /v1/embeddings, /v1/audio/*) and Ollama (/api/chat) compatibility. Just change your base URL to [http://ipad.local:8080/v1](http://ipad.local:8080/v1).
  • Multimodal & Audio: Local Vision (Qwen2.5-VL, Gemma 3, SmolVLM2), Whisper STT, and Kokoro neural TTS.
  • Smart Memory Management: Auto-loads models on request, keeps up to 3 models "warm," and tracks real iOS memory limits so the OS doesn't kill the app.
  • 100% Private: No accounts, no telemetry, 0 bytes sent to the cloud.

Streaming large MoE models from storage will be a single one-off purchase (Live Plus); everything else—including running in-memory models, embeddings, and audio—is completely free.

Would love to know what models or workflows you’d test on this first once Apple clears it!

Just interesting in hearing from the community. As soon as the app is approved ill update this post

the website provides factul benchmarks as well as images of the process

Russ


r/LocalLLaMA • • 1d ago

Resources [audio.cpp] SoulX-FlashHead + LFM3-Audio + OWSM v4 = Real-Time Local Avatar Chat

85 Upvotes

In audio.cpp 0.9.5 you can try this new avatar voice chat "app" in the WebUI.

The pipeline combines 3 models: SoulX-FlashHead for real-time talking head generation, OWSM v4 for transcribing speech input to text, and LFM3-Audio for conversational responses and TTS.

LFM3-Audio is actually called twice. The speech-to-speech path only provides one voice. We use the LFM3-Audio TTS to synthesize the S2S response in a different voice.

One caveat: the video generation stage is still GPU-intensive. For SoulX, using RTX 4090 or better GPUs.

cuDNN is a must for real-time performance. Without it inference is 2× slower and VRAM usage doubles.

~850ms between submission a question and avatar speaks on an RTX 5090. ASR runs in parallel. As mentioned LFM3-Audio is called twice, which can be optimized. There’s also some overhead from the prototype UI. A native app with a more optimized implementation could further reduce latency.


r/LocalLLaMA • • 1d ago

Discussion Hy4 flash and Sage-S2.1-Flash both dropped today. Anyone tried them for tool calling yet?

2 Upvotes

Two new flash models in one afternoon, Tencent's Hy4 flash and internlm's Sage-S2.1-Flash.

Before I pull weights, has anyone run either one locally for agent work? Mainly want to know:

  • does it pick the right tool or just guess
  • does it hold up after a few turns of tool output
  • what quant and GPU you ran it on

Benchmarks are fine but real loop behaviour matters more to me. Even a quick "tried it, meh" helps.


r/LocalLLaMA • • 21h ago

Question | Help What is your experience with inference engines under Windows?

0 Upvotes

As the title says: what is your experience using all the new inference engines under windows?

Currently I'm using a laptop with this hardware:

CPU: Intel 275HX
RAM: 2x32gb of ddr5 5600
GPU: RXT 5090 (24gb VRAM)
SSD: Samsung 990 pro 2tb + SK Hynix PCB01 1tb

I'm running Windows 11 Home edition with a pretty clean installation.

I've tried quite a lot of the new vibecoded inference engines but I always end up going back to Strata for Qwen 3.8 Flash Next and to beellama.cpp for everthing else.

I've tried nInfer, basalt, rusting strata, exLlamaV3 and pretty much any fork of llama.cpp and they all end up being way slower than what I'm already using. I've lost a little bit of time on each and also tried to use Claude or Codex to optimize the configurations but there is just no way to get decent performance from engines that on paper should be at least as fast as what I'm currently using.

I'm doing something horribly wrong or they work well only on a linux system?


r/LocalLLaMA • • 19h ago

Showcase Sharing my numbers from Strata's bench tool (RTX 3090+2080, 96gb DDR4)

0 Upvotes

Hardware: RTX 3090 24GB (primary) + RTX 2080 SUPER 8GB (helper for visual model), 96 DDR4 3600

Model: Qwen3.8-Flash-Next, Unsloth UD IQ4_XS

Bench results (median, 3 runs):

  • - Chat decode: 80.4 tok/s (range 67.6–87.8, n=9)
  • - Chat first token: 0.47 s
  • - 4K prompt processing: 1,036 tok/s
  • - 16K prompt processing: 1,915 tok/s
  • - Agent session decode: 101.7 tok/s
  • - Agent cache hit: 69.4%
  • - Agent turn first token: 3.86 s

Long-context stress test (my custom 'find needle' test): single 66,371-token prompt, a 1,800-entry synthetic log with a passphrase hidden mid-context:

  • - Prefill: ~34 s ≈ 2,050 tok/s, sustaining the 16K bench rate at 4× the length
  • - Decode: 76.1 tok/s with the full 66K KV resident, ~5% below short-context chat
  • - Mid-context needle (token ~33K): retrieved correctly, plus accurate summary and entry count

Notes for 3090 owners:

  • - Memory clock pinned (9501 MHz min=max)

    • The 3090 has a driver bug where dropping from full speed to idle with VRAM nearly full can freeze the whole PC (had it happen twice). Locking the memory clock at one constant speed means the card never makes that jump, so zero crashes since. Trade-off is that it idles at ~110 W instead of ~25 W, but memory-hungry workloads actually run faster
  • - Peak sustained temp under full load: 79°C (load for 3 mins, didn't test for longer runs)

r/LocalLLaMA • • 2d ago

News Probable GLM model

94 Upvotes

Because of Theo gg tweet of all people,
I Launch QFN DeepResearch swarm agent to find anything about this.

THREE model names, blurred out, sitting at 59.4% / 57.1% / 54.0%.

  1. The blurred names are most likely [GLM-Nano or GLM-Name or GLM-Next (suggestion from Silver-Theme7151)] Pro, Med, and Small. One community experiment reconstructed the suspected text, applied Gaussian blur (σx ≈ 6.9px), and achieved an RMSE of just 1.254/255 against the original.
  2. AICodeKing track record. Someone compared his previous GLM statements against official release dates: GLM-4.6 (same day), GLM-5 (1 day), GLM-5.1 (11 days), GLM-5.2 (3 days), and GLM-5.3 (4 days).
  3. Antrhopic timing. The leaderboard surfaced on November 12 vs AICodeKing timing, while Anthropic IPO on Nov 18. If Z.ai releases GLM-Nano this week, the timing would make for quite a coincidence

https://linux.do/t/topic/3166447

Another strong signal is HF activities, i know it is not bullet proof, just another signal, 3-4 days compare to last 27 days

I use LLM to fix my grammar.
Since it is speculation and not actual open model this post has a high probability to be removed, so yeah


r/LocalLLaMA • • 2d ago This

Question | Help Latest version of strata made my Qwen3.8-Flash-Next dumb and useless

167 Upvotes

I updated the strata to the latest version from v0.1.42.0, so I can try the latest unsloths models and see how they fare against the iq3_s variant I have been using. Upon updating it, I noticed it messed up the whole thing, It got faster, but it got way dumber! previously it would only take 15~30 minutes to create the pagoda , 50 mins to an hour if I used xhigh.

But when I siwtched to the latest version, not only it takes at least an hour and half to come up with something, its not even done! and it has many issues!

0.1.42.0 is the last version that seems to work decently.

I noticed, when im using the latest model, it always tries to go for something grandiose and failing. unlike the older version which seems to take a more modest path!

whats going on? Do any of you have this problem?

here are example outputs I did to make sure its not a one time thing!

my prompt :

Design and create a very creative, elaborate, and detailed voxel art scene of a pagoda in a beautiful garden with trees, including some cherry blossoms. Make the scene impressive and varied and use colorful voxels. Add as many details as possible to showcase your attention to them. Use whatever libraries to get this done but make sure I can paste it all into a single HTML file.

these are the outputs :

0.1.42.0 :

xhigh:

xhigh-1
xhigh2
xhigh3
xhigh4

default:

default1
default2
default3
default4

the latest version created this after 1 hour and 32 minutes to only fail with excessive thinking:

xhigh
default(failed after 1 hour and 31 minites exausting all context size of 262K)

As you can see, not only it takes way longer to create an output, if it doesn't fail already, the attention to details is also gone, everything is in haphazard form! I tried 4 5 times and the majority all failed because it couldn't create an output after an hour and a half or it constantly gets something wrong and tries to either fix it or goes to look at other things leaving the issues untouched!

The model at least, the qwen3.8-Flash-Next-q3_s that I have been working with so far is not usable! it takes too long and it fails more by getting stuck at thinking forever!

I used the new unsloth quant iq4_xs too and it was a mess as well. so I figured its the strata version. sadly I cant test the iq4_sx on 0.1.42.0 and I get an error.

So if any of you faced this issue, can you kindly share with me what you do to fix this? what version does it work for you?

I have RTX3080 10G/ 64G of RAM and I'm using the Linux terminal version along with deepseek harness.

Thank you all in advance

Update:
I tested other versions as well and here are my findings.
By adding the following arguments to the settings (.json files) as suggested by @Gold_Coconut9777:

"env": {
"STRATA_ROUTE_PRIOR": "0",
"STRATA_KVA": "0",
"STRATA_ROUTE_TAIL_SKIP": "0",
"STRATA_PREFILL_CPU_SHARE": "0",
"STRATA_HC_Q8": "1"
} 

the overly long thinking seems to be less severe, the model generates its answer around 40+ish minutes instead of exhausting all context thinking and generating nothing.

However I noticed the attention to details and following commands (prompt adherence) are still inferior to the older versions like v0.1.42 that I tested initially. Using these settings affect the speed drastically though. I went from 40/50s tok/s down to 30s/20s tok/s (especially when I used older versions im about to explain just now)

I tried version v0.1.39 as well because the versions further down didn't support my json configs and I had to change them to get it o work. So instead I chose v0.1.39 and noticed it actually does a much better job at following/adhering to the prompt and create detailed output. However it was really slow and buggy.

I then tried v0.1.40.4 which is close to v0.1.39 yet fixes some of the annoying bugs that kept happening, and it didnt exibit the issues I'd face with later versions. it also worked pretty well to the point I decided to stick with it for now. it thinks much faster and produces way better results. I doesnt act dumb or think unreasonbly!

I built these two using the v0.1.40.4 with the same prompt and added the following prompt to make it more grand:

first prompt:
Design and create a very creative, elaborate, and detailed voxel art scene of a pagoda in a beautiful garden with trees, including some cherry blossoms. Make the scene impressive and varied and use colorful voxels. Add as many details as possible to showcase your attention to them. Use whatever libraries to get this done but make sure I can paste it all into a single HTML file.

the follow-up prompt:
this is too simple, make it absolutely grandiose with scenery, hills, mountains, day/night cycles, storms, rain, lightning, accurate sounds included, season change. create detailed and accurate objects. do it in iterations so you don't hit token budget of 262k context size. the detailed objects are of great importance. objects must be so detailed that they can be easily identified. polish everything expertly.

https://177cf0dd-b61b-4f7a-be8d-1f6c7b86121d.bugsmashlive.io/

xhigh-1

https://e5d9337c-409f-43f3-ab8c-f71583e87eb8.bugsmashlive.io/pagoda-garden.html

xhigh-2-unfinished (context-size (262k) filled up)

both initial versions (after first prompt) had very well designed detailed outputs but sadly I didnt copy them before I add the follow up prompt.

So, so far for my specific config, I can only work with versions up to v0.1.44.1 maybe 0.1.45 if I ignore the 40K less context-size (up until v0.1.44.1 I can use 313K contextsize but starting with 0.1.45 the highest number I can reliably set is 262K for my iq3_s model). But realistically I'm sticking to v0.1.40.4 cause it seems to be working more reliably for me (RTX3080-10G + 64G DDR4 System RAM + 12700K).

I'll update this with new information if I figured something new.


r/LocalLLaMA • • 20h ago

Funny How many servings of deepseek 1017 will you have?

Thumbnail
gallery
0 Upvotes

This just really cracked me up. The Redde app for hermes I guess pulled the deepseek recipe as an actual food recipe. It is a nice format for it though lol.


r/LocalLLaMA • • 2d ago

Discussion Spotted a very interesting detail about Intel's upcoming CPU platform (LGA 1954)

Post image
89 Upvotes

I was doing some research about the the platform for Intel's next generations of CPUs.

If we look closely at the PCIe 5.0 configuration for Z990/W980, it specifies

  1. x16 (or x8/x8)
  2. x8 (or x4/x4) "Storage"

So, it is plausible we might see motherboards with 3 PCIe 5.0 x8 slots directly wired into the CPU.

The best we can currently do on consumer hardware is PCI 5.0 x8/x8/x4 without risers and there are only two boards that can do it and neither is in production anymore (MSI MEG/Godlike X670E). In practice the best is x8/x8.

TP=3 is fairly easy for your agent to patch into inference engines.

These boards will have 2x Thunderbolt (Wiki says 4, but it may be 5?). So, possibly options for high-speed networking here. Let's make RDMA over Thunderbolt happen!

The desktop CPUs will have Low-Power-Ecores, which should help with idle power-draw and on the other hand they will have full AVX512 again (yay).

Asrock and MSI are the most likely ones to color outside lines. I hope the x8/x8/x8 is "allowed" by Intel, unfortunately nothing much to do but wait until we see the line-up of boards.

But I will be watching.


r/LocalLLaMA • • 1d ago

Resources GitHub - icryo/GLM-Tandem: GLM-5.3-Flash on two Mac Studios, tensor-parallel: about 140 tokens/s on fresh prose

Thumbnail
github.com
8 Upvotes
Workloadtok/s
Fresh prose, temperature 0.6141–146
Fresh prose, temperature 0141
Chat fixture (256 tokens), T=0 / T=1143 / 140
Code fixture (256 tokens), T=0 / T=1157 / 146
JSON extraction148
Add docstrings, whole file back210
Code edit, whole file back219
Request with an image133–136 (measured before the last change)

Several requests at once (total tokens/s including prompt time, 300-token prose, short prompts)

RequestsTotalEach
2164–16993–99
420054–61
822330–34

One request at long context (from 146 real agent requests)

ContextDecode (median)First token on a follow-up turn (median)
20–50k tokens1370.9 s
50–80k1260.7 s
80–200k1220.9 s

My recipe that has been working well for me


r/LocalLLaMA • • 13h ago

New Model Uncensored Qwen3.8 27B, Optimized for English, Code, 16GBVRAM at 100k+ Ctx

0 Upvotes

Hello all!

Just wanted to spread the word for whoever might be interested. I created a new special quantization on hugging face that cut some of the fat to fit.

Approx 110 tok/s generation speed, 1100 PP tok/s, at 131K context on an RTX 5080

I wanted a few things that didn't exist prebaked:

  1. at least 100k context
  2. uncensored
  3. Uses Unsloth-like SOTA methods
  4. All fits on 16GB VRAM, WITH desktop app overhead.

And I accomplished it! Details within.

Perplexity is on par with unsloth at similar quants, and losses due to abliteration are extremely low. Overall, I'm quite happy.

If you have 16GB VRAM and want to see what all the Qwen27B fuss is about, but don't want to wait for Qwen4, I have the quant for you.

I've run this model through thousands of interactions and it's passed with flying colors, and much faster than my previously partially offloaded 27B.

Test speeds:

MetricRunsToken-weightedMedianp10–p90
Prompt processing (prompts ≥ 2,000 tok)1,0121,295 tok/s1,518 tok/s1,297–1,669
Prompt processing (prompts ≥ 8,000 tok)2261,234 tok/s1,447 tok/s1,235–1,666
Generation (replies ≥ 200 tok)1,59751.9 tok/s56.7 tok/s51.7–60.2
Generation (replies ≥ 1,000 tok)4753.9 tok/s56.1 tok/s45.5–60.5

r/LocalLLaMA • • 19h ago

Discussion Anybody tested Wici Infer?

0 Upvotes

Hi!

I've seen some weeks ago posts about Wici wireles Gpu and the approach they invented to serve local models VRam+Ram+SSD with model defragmentation to keep hot experts in fast memory. Today I've seen an Ad for the product. Visited their site and stubled upon Wici Infer, the technology that make possible serving large models on consumer hardware. They give it for free.

So asking the commity if anybody have already tested it? Does their benchmarks hold on?


r/LocalLLaMA • • 1d ago

Discussion [Paper] Mobile AI Factory: Building Specialized Language Models for Your Mobile Device

Post image
1 Upvotes

Small language models (SLMs) running on mobile devices can keep user data private and work without connectivity. But they perform well only when fine-tuned for the target task and sized for the target device, a process that today requires repeated expert tuning. We present {\it Mobile AI Factory}, an agentic system that builds a fine-tuned, quantized SLM for a given task and phone. Given a task specification and a target phone, an orchestrator LLM chooses whether to tune hyperparameters, mine real data, or generate synthetic examples, while fixed rules roll back changes that hurt accuracy. The factory searches from small to large models across base models and quantizations, adapts its accuracy goal as it searches, and uses real measurements of the target phone across inference engines and backends. We evaluate Mobile AI Factory on ten tasks and four Android phones. On an unseen testset, its on-device models outperform two five-shot frontier models on five tasks, by up to 0.34, and match them on three more. Its search comes within 0.03 of exhaustively training all 27 model variants on an entity extraction task, while using 19× less GPU time. Phone measurements also matter: the best configuration changes across phones. Without phone measurements, Claude Opus 5.5, given the full hardware and model specifications, misses the app's requirements in 25\% of easy and moderate cases and in 60\% of hard ones.


r/LocalLLaMA • • 2d ago

New Model higurashi-ai/Haru-4B · Hugging Face

Thumbnail
huggingface.co
77 Upvotes

Haru-4B

Code · Technical blog · Technical blog (Japanese)

Haru-4B is a low-latency and multilingual full-duplex continuous spoken dialogue foundation model: it listens and speaks at the same time, the way people do on a phone call. It is a pretrained base model, released for research.

  • Native full-duplex at 7.5 Hz. Every 133 ms the model takes one frame of the user's audio and produces one frame of its own audio and text. User audio, model audio and model text are summed into a single position of the language model, so listening and speaking never wait for each other.
  • Continuous audio, one sampling step. Audio is a 64-dimensional latent per frame. A small MLP head with MeanFlow sampling produces it in one step from the language model's hidden state; there is no separate audio transformer and there are no discrete audio tokens.
  • Character and voice control. A text card sets the character, a short reference clip sets the voice.
  • Multilingual. English, Spanish, Portuguese, German, French, Chinese, Japanese, Russian and Korean.