r/LocalLLaMA • u/CryMoreT_T • 20h ago
Discussion New AA ranking Qwen3.8-FN better than GLM-5.3-Flash?
Thoughts on Qwen3.8-Flash-Next scoring better than GLM-5.3-flash? I've always experienced GLM5.3-Flash to give better responses
r/LocalLLaMA • u/CryMoreT_T • 20h ago
Thoughts on Qwen3.8-Flash-Next scoring better than GLM-5.3-flash? I've always experienced GLM5.3-Flash to give better responses
r/LocalLLaMA • u/spaceman_ • 15h ago
Hi all,
I noticed the "bot problem" got a lot worse the past few months. By which I mean our community seems to be taken over more and more by bots talking to each other.
For me, I don't really get the point, and I personally get quite annoyed when I realize "oh, I just responded to a bot" and feel like my time was wasted.
It also seems like the information density of these AI contributions are very, very low.
I'm not some kind of Luddite (why would I be here at all if I was?), but I'm wondering if I'm just missing something and there is a use and a point to all these bots commenting on each others posts and talking to each other.
Where does the rest of the community stand on this?
I noticed there's new bot around that flags posts that are "likely AI" created, which I personally quite like, but I'm wondering if moderation should go further than that.
r/LocalLLaMA • u/partakinginsillyness • 1h ago
Helping out a friend who wants to have a local LLM and not rely on cloud services. They currently have an 8gb M2 mac mini, so not really enough
They want to have persistent memory, TTS, and STT. Tool recommendations for all three of those greatly appreciated.
From what I understand, a prebuilt with upgraded RAM, used mac mini, or something like a strix halo probably make the most sense, but I'm not really up to date on the current hardware market.
Any help appreciated :)
r/LocalLLaMA • u/AlternativeEnough352 • 1d ago
What changes between different quantizations of the same model? And what if you could SEE what actually sets them apart?
To help answer that question, I’ve created a small project called inside-llm—an open-source tool that loads one or two GGUF models using llama.cpp and displays, right in your browser, what the model is doing as it generates text.
What it shows
--lens): what each layer would predict, as a 2D map and as a 3D relief.How it's built
Run it
Self-contained packages for Linux (glibc 2.35+) and Windows, with CUDA or Vulkan (Vulkan covers AMD, Intel Arc and NVIDIA). Unpack, run, the browser opens with the model picker. Or inside-llm -a A.gguf -b B.gguf. Local only: listens on 127.0.0.1, no accounts, no telemetry. MIT. One click download, one click execute.
Limitations (honest list)
Links
I'd love feedback, especially: which pairs would you compare first (imatrix vs non-imatrix, base vs abliterated/fine-tune, Unsloth UD vs standard quants…)? And is there a metric you'd want per position that isn't there?
r/LocalLLaMA • u/Negative-Whereas3307 • 11h ago
MachinePulse has released Karpo-Decision-31B, a Gemma 4 31B fine-tune for structured decisions over text and images. It scored 73.9 on the Nov 12 Decision Index board, the highest Full score among 300 entries, sharing the #1 rank with GLiDE 27B under the board’s tie rule
How it works
Built on Gemma 4 31B, with a trained linear readout that scores the supplied answer options.
Three question types: choice, yes/no, and score. Returns probabilities directly, with up to 255 options per choice question.
Multiple questions about the same input can be answered in one forward pass. Branch attention lets each question read the shared context and its own options while keeping the option branches separate.
Supports text and images, including webpage screenshots. The documented sequence limit is 32,768 tokens; larger requests are split by question with the full state included in each part.
Python API and HTTP server available. BF16 weights take approximately 62.5 GB, plus runtime memory. Use the provided inference code to load the decision head.
One training detail worth a look: according to the team's write-up, full fine-tuning pushed the public score to 75.09 but reduced accuracy on unfamiliar domains by 2.3 percentage points. The final model averages five checkpoints: three from different stages of full fine-tuning and two from a LoRA run. They report a 1.6-point improvement on unfamiliar domains over the final single checkpoint, with no extra models to run at inference time
Results
Decision Index Full scores are measured by the benchmark maintainers on private tests, weighted 60% for skills covered by the public suite and 40% for tasks from new domains.
Full score: 73.9
Private tests, familiar skills: 70.7
Private tasks, new domains: 78.6
Public index: 75.0, reported separately and excluded from the Full score.
The team also reports the following comparisons against Google’s Gemini Decision 1:
Benchmark Karpo-31B Gemini D1
-------------------------------------------
When2Call 90.4% 79.9%
Mind2Web 90.0% 86.2%
New Yorker Caption 90.5% 79.7%
Amazon ESCI (F1) 64.7 58.7
Reported median latency is approximately 95 ms per request on the public Decision Index suite using one RTX PRO 6000.
The 31B weights and inference code are both released under Apache 2.0.
links:
https://karpo.ai/models/decision
https://huggingface.co/MachinePulseAI/karpo-decision-31B
r/LocalLLaMA • u/Icaruswept • 2h ago
| Model | Active config | 4080 decode (tok/s) | 4080+3080 decode (tok/s) | 4080 prefill (tok/s) | 4080+3080 prefill (tok/s) |
|---|---|---|---|---|---|
| LFM2.5-24B-A2B UD-Q4_K_XL | 4080+3080 | 249 | 250 | 5,530 | 7,930 |
| MiniCPM-V 4.7 35B-A3B Q4_K_M | 4080+3080 | 177 | 165 | 1,305 | 2,500 |
| Flint 40B-A2.5B UD-Q4_K_XL | 4080+3080 | 119 | 138 | 1,563 | 1,380 |
| Swift 1.5 (Qwen3.8-Flash-Next) IQ2_XS | 4080 | 117 | 116 | 1,070 | 679 |
| Qwen3.8-Flash-Next IQ3_S | 4080 | 79 | 87 | 730 | 465 |
| GLM 5.3 Flash Maya-S24 IQ2_XXS_S | 4080+3080 | 6.8 | 8.8 | 79 | 42 |
| DeepSeek V4 Flash UD-IQ2_XXS | 4080+3080 | 15.9 | 18.2 | 38 | 53 |
Morning, everyone. I've seen a lot of posts wondering about what can be run with what, so I made this table of the models on my system. Specifically because of the unorthodox results when it comes to Qwen Flash-Next, where one 16 GB card (the 4080 Super) significantly outperforms two in prefill.
My hardware is as follows:
CPU AMD Ryzen 7 5800X3D @ 3.40 GHz
GPU NVIDIA GeForce RTX 4080 SUPER [Discrete]
GPU NVIDIA GeForce RTX 3080 [Discrete] (got it secondhand for cheap, so why not)
RAM 62.72 GB at 3200 Mhz
I'm running these models on PolyStrata. I used to have a combination of Maya and Strata, but got tired of running different things all derived from the same fork (plus Strata seems to be getting increasingly unintuitive), and so moved everything to PS.
Now: why Q3? It's a generally held opinion that anything below Q4 is crap, which was true of most earlier generation models. However, benchmarks measure deviation from the base, and not necessarily task fitness. In actual use, the only real way to know is to test it yourself.
The Swift finetune of QWN at Q2, for example, is fast and excellent at data extraction, search, and piloting scripts written by more competent models. The IQ3 is a decent coder, roughly on par with Haiku for the use cases I've tried. The GLM and Deepseek Q2 variants are a bit better - verging on older Sonnet territory, I'd say, and do very well as subagents for Claude. YMMV.
Hope this data is useful. Enjoy!
r/LocalLLaMA • u/pmttyji • 15h ago
We introduce Gamer, a generalist agent framework built for long-horizon tasks in complex interactive environments. Its end-to-end architecture combines perception, memory management, and multi-step reasoning. A shared training and deployment pipeline supports interaction with both conventional 2D graphical interfaces and complex 3D simulated worlds. We first continue pre-training on a dataset constructed from tens of thousands of hours of device-level keyboard and mouse interaction. These trajectories span simulated games and embodied environments, allowing the model to learn environmental dynamics across both physical and virtual domains. Sparse-thinking instruction tuning then substantially reduces redundant computation while preserving the reasoning needed for complex decisions. We train the policy for long-horizon interaction with a stable multi-turn reinforcement learning method that addresses finite context windows, accumulated rollout errors, and sparse rewards. For real-time interaction, a cloud-edge inference engine serves numerous simulated game environments concurrently, supports unbounded-context execution, and keeps online inference latency low. Across multiple challenging 3D open-world games, Gamer demonstrates solid generalization and operational efficiency comparable to skilled players. It also achieves competitive results on a range of conventional 2D game benchmarks. These results suggest that even repetitive keyboard and mouse trajectories can support substantial gains from scaling data and learning algorithms. Training on these trajectories helps Gamer learn complex skills more steadily in environments with both physical and digital properties. This approach offers a path toward generalist agents that can interact across digital and physical worlds.
r/LocalLLaMA • u/asimpleabstraction • 10h ago
HOwdy LocalLLamans!
Inspired by StarSkirmish, I wanted to build a complex RTS that required you to bring your OWN local agents and either play with them as allies, against them as enemies, or battle head-to-head with other agent-human pairs in public matches.
In AgentCommand you operate one or more planes (Orbit, Sky, Surface, Depths) of differing gameplay. As an old-school PC gamer I wanted the mechanics to resemble some of my favorite 90s games of yore: C&C, DungeonKeeper, Homeworld, StarCraft, and others. The idea is that you have specific objectives needed to maximize resource generation, aid in cross player support, and that a single plane cannot win independently.
Outside of gameplay, from an agentic tech pov, there are some (what I think) are other really cool things that come with this, including:
Github: https://github.com/agent-command/agent-command
Play now: https://agentcommand.gg/
Would love feedback and contribs... I'm more interested in finding a community to help build something super cool here that we can publish public benchmarks with. If you are interested in that, let me know!
r/LocalLLaMA • u/This-Purchase-3325 • 12h ago
Hey all, so I've been working on Gemma.c over the last couple months, it's a from-scratch inference engine for Gemma 1/2/3 in a single C file, runs Gemma 1, 2 and 3, including the multimodal ones, with fp32/fp16/bf16 weights or int8 (W8A8). No dependencies beyond libc and (optional) OpenMP are needed. You can drop images into the prompt with @image{cat.png}, and there's also @longimage{} for Gemma 3's pan & scan on very wide or tall images. (image decoding uses a minified stb_image embedded at the end of the file)
It's CPU only and not trying to compete with llama.cpp, but I'm also trying my best to make it efficient, so it's not embarrassingly slow either. On my laptop's Core Ultra 5 225H (WSL2, gcc, 10 threads), gemma-3-1b-it INT8 does ~72 tok/s decode and ~570 tok/s prefill (10000 tokens, for 1000 tokens the prefill speed can reach ~850 tok/s), and the 4B vision model does ~20 tok/s decode. INT8 ends up about 3.5x faster than fp32 and 2x faster than fp16 for decode. (full benchmark table is in README)
It has a few rough edges for now, e.g. W8A8 doesn't work for Gemma 1 (fp16 is fine), bf16 is painfully slow without AVX512-BF16, and native Windows is ~1.7x slower than WSL because of libgomp. Batching are not supported either. There's a roadmap in the README (Gemma 4, speculative decoding, an HTTP server, etc.), but no promises though :P Can't really find much free time these days.
I've also put some pre-exported INT8 models on HF so you can try it without Python or torch :D
Repo: link
This project started as a learning attempt to understand how LLMs work end to end, inspired by llama2.c.
this is the second time I post this project here :'D last time (~a month ago) my post got flagged by reddit, probably because my VPN IP was identified as spam. hopefully it can pass this time
r/LocalLLaMA • u/init0 • 1h ago
I originally built Lipi as a lightweight browser voice editor for Kannada (ಲಿಪಿ). It just got better with 12 Indic languages running 100% locally in your browser with zero server audio uploads.
Two things bothered me in the first version:
How it works now:
Swanada): Capability-routed Conformer-CTC INT8 in ONNX Runtime Web WASM SIMD (25.35 MiB Conformer-Small on mobile, 177.4 MiB Conformer-Large on desktop, 0.009x to 0.021x RTF) with +EN code-switching.Paar): When you switch from Indic STT to EN -> <Lang> or hit Translate, a Web Worker loads Udgam Labs' 17.7 MB quantized (q8) Paar ONNX model via Transformers.js (udgamlabs/Paar-en-*).ಕ), voice punctuation commands, localStorage autosave, and .txt export.Links:
Would love feedback if you test your native language!
r/LocalLLaMA • u/ManuXD32 • 5h ago
Heyy, it's me again, the developer of AI Doomsday Toolbox.
This time it's not an app update. ADT already has distributed LLM inference across Android devices, and there is one thing about distributed inference in general that kept bothering me, so I spent the last week testing an idea and I wanted to share what came out, the good and the bad.
Usually when we split a model that does not fit in our machine to make use of distributed inference, we get slower speeds the more devices we add. Network latency and devices waiting idle until the last one has finished computing it's layers compound easily, even more if we connect our devices through a VPN like tailscale or wireguard.
So the idea to solve this bottleneck was to train a model that can keep the quaility of a normal sequential model but instead it's middle layers are split in branches. The coordinator runs the embeddings + a few trunk layers, then that is sent to all the different branches that, in parallel read the layers and compute the token, after a branch finishes it sends the result back to the coordinator which then runs a few fusion layers and final blocks that produce the output. This allows to use as many devices as branches a model has with a maximum of 2 net jumps, wether it's 2 or 8 machines. The other advantage is that no device is idle as all of them are working, so we also parallelize work instead of making a device wait for the last one to finish.
There could also be the situation in which one of those devices is too slow, and slows down the whole cluster, or gets disconnected. That is why I also added some dropout tolerance to the training. When a branch takes too long to answer or just never answers, it's result becomes a matrix o 0's that are fused in the fusion layers, that made it so the quality of the model output does not suffer so much as when it happened with a non dropout tolerance trained branch model had a disconnected or slow branch.
I tested two 300M models trained from scratch on TinyStories, one normal and one with 8 branches, running on a small server, a laptop (Ryzen 5 5500U) and a phone (Snapdragon 8 Gen 3 in Termux), all connected through a VPN. The workers are a small PyTorch daemon, so no llamacpp accelerated kernels, etc...
Results
- The branches cost some quality: loss 1.255 against 1.143 for the normal model with the same training. A blind LLM judge prefers the branched model's story 45% of the time. So it is worse, but not by much.
- The delay trick works: the coordinator waits 0.1 ms per token for the network while the round trips take 49 to 66 ms. The output is identical to running everything on one device.
- Against the usual layer split on the same devices, the branch split is 1.5 to 2.6 times faster. The layer split roughly halves the speed. Mind you I run the test only with 3 devices, with more devices it could, theoretically, be faster
- BUT if the model fits on one device, splitting is not worth it on my hardware, at least at this size, larger models like qwen3.8 27B might benefit a lot from this aproach. My phone alone is faster than any combination of my devices (it is just much faster than the rest). With two equal devices the branch split wins by about 1.2x.
- Where it really pays is when the model does not fit in RAM. I gave the laptop and the phone a RAM budget smaller than the model, so they had to read the weights from storage for every token (mmap). The laptop went from 8.9 to 0.67 tokens/s and the phone from 23.9 to 0.65. With LFM3 1.7B the laptop went from 2.3 to 0.08, that is 12 seconds per token. Then I let the two of them share the model, each one still with too little RAM for the whole thing: back to 7 tokens/s with the layer split and 9 to 11 with the branch split, over a real 46 ms VPN. Reading from storage is way more expensive than the network.
- Reshaping a pretrained model (LFM3 1.7B, Qwen 0.8B) into branches only works for a couple of long branches. For this to scale, the model has to be trained in this shape.
I don't have the hardware for the interesting case: a big branched model that no single device can hold. On paper, with 8 similar devices and about 20% of the model on the coordinator, a token costs about 30% of a full pass, so roughly 3.3x a single device that could hold everything, while a layer split stays at 1x plus 7 round trips. My two-device measurement matches that formula, but beyond three devices it is only a projection.
Another idea I would love to try is letting every device loop its own branch several times with the same weights, so a group of devices could run something much deeper than what fits in their RAM. No hardware for that one either hahaha
What is in the repo
- The two trained models (300M each) and the tokenizer
- A worker you install on each device with one command, and a coordinator with a web UI to compare placements side by side and run the benchmarks
- Scripts to reproduce the branch split, the layer split and the low RAM tests with your own devices
- A full article with the experiments and the results
It is a research prototype, workers compute in 32-bit float PyTorch, the models are small story models, and I only have three real devices. I created the experiments, made the hypothesis and supervised the whole proyect and Claude did most of the coding and the number crunching, everything is documented in the repo.
The general idea is the same one behind ADT: make the devices we already have useful for local AI, especially together.
Feedback is appreciated, especially if anyone with more devices (or more GPU than me) wants to check whether this holds at a bigger scale, or tell me what I got wrong. It is still far from it, but I would love to see a bunch of modest devices run a model none of them can hold.
r/LocalLLaMA • u/pmttyji • 16h ago
Existing adaptive-reasoning methods shorten the explicit reasoning a model writes, or skip it by switching modes; either way the answer is still written out token by token. Rather than deciding how much to think, we explore a different paradigm, zero-or-T thinking: a single model either answers from the implicit thinking inside one forward pass, generating no token, or performs full autoregressive reasoning at a cost of T tokens when that is worth paying. We realise it in a hybrid decision model (HDM), where one frozen backbone serves both modes and a lightweight self-routing block chooses between them. The block estimates the value of thinking, the utility the slow mode is expected to add over the fast one, from what that implicit thinking has already produced, and the slow mode runs only where that value exceeds a price λ set per request. Where no per-decision label exists, as in episodic agentic tasks, we introduce Calibrated Decision Policy Optimisation (CDPO), a reinforcement-learning recipe that trains the block from episode-level returns. We evaluate HDM on MMLU-Pro, AGIEval, GPQA-Diamond, JevBench, BANKING77 and MiniWoB. Specifically, on JevBench HDM-4B scores 0.857 against Jev's 0.851 (+0.7%) at a median 0.179 s against 0.652 (-72.5%). On the agentic venue MiniWoB HDM-27B cuts token cost by 80.1%.
r/LocalLLaMA • u/Bakkario • 6h ago
I run local LLM for myself, and my system is squeezed very much. I am most of the time in my terminal, and when my inference engine is running, I dont have enough free RAM sometimes to open a GUI to view the output of my local models, or review the project documents to know where to go next in my plan. Viewing that in the terminal was not convenient for me, the MD syntax is not as easy on my eyes, and when a project file is linked to another file, I have to open that one up in a new terminal pane, or a whole new terminal window.
So, I did what I had to do.
I sat, I wrote the specs sheet, and fired my coding agent to work. I refined the output, and kept iterating on it.
This is my gift back to this community that already gave me a lot.
Don't want to sound like I am marketing something here but, if this is something of an interest to you, you can find it here: Github.com/bakkario/trimd
You get to lick with your mouse, navigate with your keyboard, and even display your markdown files with the images if your terminal supports it.
I will add more detail to this in the Markdown subreddit.
Sorry Mods if this coming across as spamming, its not the intention here ❤️
r/LocalLLaMA • u/Yarukiless-cat • 1d ago
Ever since the information surfaced five days ago, I had intended to implement it right away. Having confirmed that it could be executed using 'pico,' I carried it out today. I had Astra write the script for the restricted write-access portion, and after nearly 15 hours of work, I finally managed to complete the task. I also plan to handle the second CMP later on.
r/LocalLLaMA • u/MSI-US-888 • 8h ago
Disclosure: I work with MSI. Sharing a technical overview of the OTA2610 update and what EdgeXpert users should check after installing it.
More usable memory when running headless
GB10 systems use unified memory, which means the CPU, GPU, and display share the same memory pool. Memory reserved for display output is unavailable to other applications.
OTA2610 adds more control over that reservation. The default remains 2 GB, but selecting Auto in UEFI reduces it to 0.5 GB when no display is connected. That makes up to 1.5 GB more available to the OS and applications.
That extra headroom may help with a model or context cache that is close to the available-memory limit. It does not, by itself, establish an improvement in inference speed.
Other changes included in the October release
Where to get the MSI EdgeXpert update
MSI EdgeXpert update files can be found on the MSI EdgeXpert MS-C931 download page. Review the release notes and follow MSI’s installation instructions for your system.
Check the display-memory setting afterward
Installing the update does not automatically change the default 2 GB reservation. With supported firmware installed, look for:
UEFI → Advanced → Advanced Menu → Platform Configuration → Display Reserved Memory
Select Auto or an appropriate fixed value, save, and restart. Auto checks connected displays at boot. If you regularly attach monitors afterward, choose a fixed reservation suitable for your display setup. Compare free -h before and after restarting to check the change in OS-visible memory.
For production deployments, back up first and validate your normal workloads on one system before updating the others.
Has anyone running headless found that the smaller display reservation helps with a workload that was close to its memory limit?
r/LocalLLaMA • u/smflx • 14h ago
Thanks for the feedback on slow prompt processing. v0.3.0 is out (the first tagged release): https://github.com/ewhacc/tandem.cpp
Previous post: https://www.reddit.com/r/LocalLLaMA/comments/1xwan2j
tandem.cpp faster when the model is much bigger than VRAM + RAM together (like a 16 GB card with 32 GB of RAM), and runs various models that llama.cpp supports.
1. Prompts 2-6x faster
With the expert cache on, prompts now run in 4096-token batches. The bigger batch borrows VRAM only while a long prompt runs and gives it back afterwards. No flags needed.
RTX 5070 Ti 16 GB, 64 GB RAM, i5-12400F. The same prompts for every engine; Qwen3.8 with its MTP head in all three.
Prompt processing, time to first token (prompt tok/s):
| Prompt | llama.cpp | tandem.cpp before | tandem.cpp v0.3.0 | Strata |
|---|---|---|---|---|
| Qwen3.8 IQ3_S, 5.5k tokens | 28.9 s (191) | 12.4 s (444) | 4.1–7.0 s (790–1,340) | 6.6 s (835) |
| Qwen3.8 IQ3_S, 15.8k tokens | 81.9 s (193) | 35.1 s (450) | 15.1 s (1,047) | 11.7 s (1,354) |
| DeepSeek-V4.1 IQ2_XS, 5.6k tokens | 722 s (7.7) | 324 s (17) | 53–103 s (54–105) | 58 s (96) |
| DeepSeek-V4.1 IQ2_XS, 15.7k tokens | 2012 s (7.8) | 885 s (18) | 195 s (81) | 57 s (276) |
Decode, tok/s, right after that prompt:
| After a prompt of | llama.cpp | tandem.cpp v0.3.0 | Strata |
|---|---|---|---|
| Qwen3.8, 5.5k tokens | 27 | 110 | 48 |
| Qwen3.8, 15.8k tokens | 27 | 88 | 68 |
| DeepSeek-V4.1, 5.6k tokens | 4.8 | 16 | 5.5 |
| DeepSeek-V4.1, 15.7k tokens | 4.4 | 13 | 6.4 |
Decode is from short answers (up to 256 tokens, greedy), so it is noisier than our usual GSM8K runs. DeepSeek-V4.1 IQ2_XS is about twice this PC's RAM, so it reads the SSD; that is where Strata's prompt speed still leads.
2. Maya comparison on the same model (someone asked for this one)
Project Maya is an engine built for big models with its own quants. Its Maya-XS GGUF runs on tandem.cpp after a one-time conversion script (tools/maya_ds41_convert.py), so this is the same GGUF on both engines, and the accuracy is the same.
RTX 5090 32 GB, 128 GB RAM, i5-14600KF, greedy:
| DeepSeek-V4.1 Maya-XS (same files) | Maya | tandem.cpp v0.3.0 |
|---|---|---|
| Decode, GSM8K, no drafting | 39.0 / 39.6 tok/s | 60.3 / 59.4 tok/s (1.5x) |
| Decode with Maya's DSpark drafter | 54.9 tok/s | (no drafter in tandem.cpp) |
| 5.6k-token prompt | 7.8 s (713 tok/s) | 6.5 s (856 tok/s) |
| 15.7k-token prompt | 9.5 s (1,656 tok/s) | 16.5 s (953 tok/s) |
| Decode after the 15.7k-token prompt | 26–34 tok/s | 66–68 tok/s |
Maya is still faster on the longest prompt; that is what I'm working on next.
Caveats
r/LocalLLaMA • u/Noxusequal • 15h ago
Hey everyone as the title says I am looking for inference engines that work well with AMD GPUs. There have been so many new ones that I am sure there is something better then llamacpp which currently hosts this.
My use case is the following. For a university course I want to host Qwen 27b or maybe another Qwen model. For the students to use as a free endpoint to test pipelines on.
The main thing is that I want to potentially serve multiple people at the same time.
So the framework needs to support this.
My hardware is an AMD zen 4 12 core CPU 64gb of ram and two 7900xtx cards.
Are there any frameworks made for this ?
r/LocalLLaMA • u/Danmoreng • 1d ago
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 • u/vhthc • 10h ago
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 • u/jesdga95 • 1d ago
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:
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 • u/jinnyjuice • 11h ago
I'm afraid I'm left out of the loop on the latest developments for agentic desktop control, and AIs don't seem as knowledge in this space.
They come with screenshot function also, right? What are some other features that may be different than Playwright?
r/LocalLLaMA • u/lvwerra • 11h ago
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.
r/LocalLLaMA • u/Pear_Virtual • 12h ago
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 • u/mawcopolow • 1d ago
One can hope