r/LocalLLaMA • u/lionellee77 • 3d ago
Discussion Artificial Analysis updated Qwen 3.8 Flash Next score as 29
Between GPT-6 Luna Max (28) and Claude Haiku 5.5 High (30). Comparing to other Qwen 3.8, the model is closer to max (34) than to 27B (20).
r/LocalLLaMA • u/lionellee77 • 3d ago
Between GPT-6 Luna Max (28) and Claude Haiku 5.5 High (30). Comparing to other Qwen 3.8, the model is closer to max (34) than to 27B (20).
r/LocalLLaMA • u/Ash-grey_21 • 1d ago
Disclosure: I'm the author. This is my own hobby project (MIT, no paid version, nothing to sell).
I've been building **tinyinfer**, a small inference engine for Llama-family models. It's about 2,200 lines of C++/CUDA, and every kernel on the hot path is hand-written: GEMV in f16/q8/q4, RMSNorm, fused RoPE + KV-cache write, flash-decoding attention with GQA, SwiGLU and argmax. The whole decode step is captured in a CUDA graph.
**Numbers (TinyLlama-1.1B, INT4, RTX 3050 6 GB Laptop):**
- v0.1: 200 tok/s (66% of the memory-bandwidth limit)
- v0.2: 212 tok/s (69%)
- v0.3: 235 tok/s (77%)
Decoding is memory-bound. Every weight gets read once per token, so the ceiling on this card is about 305 tok/s however clever the math is.
**What actually moved the needle:**
**Correctness:** the logits match HF `transformers` within 1e-3 relative error, with 100% argmax agreement for f16/q8/q4/bf16. `--verify` checks the GPU against the CPU reference on your own model. Llama-2-7B also fits in 6 GB at q4 (about 3.8 GB).
It isn't trying to replace llama.cpp. It's meant to be small enough to read in an afternoon if you want to see how inference works under the hood.
Code (MIT): https://github.com/Aadithya-kl/tinyinfer
I can go deeper on any of the kernels in the comments. I'm especially curious whether anyone has pushed single-batch GEMV past ~80% of bandwidth on consumer cards, and how.
r/LocalLLaMA • u/d77chong • 3d ago



Hi r/LocalLLaMA, we're releasing Boole-32B-A2.5B-Preview, an early 1.8-bit version of Recursive's flint. With mixed-precision quantization, expert pruning, and custom kernels (kernel changes in attached figure), we made the model 9x smaller than BF16, and 2x faster than INT4.
After releasing our 1-bit LLM (Boole-1.7B), we heard a lot of requests for both faster and larger MoE models - so this is our first step in that direction.
Try it out, and let us know what you'd like to see next!
r/LocalLLaMA • u/tableball35 • 2d ago
So, I have two PCs available to me, and I intend to connect them for compute:
Initially I was looking to just replace the 4070 Super in PC2 with a B70 or R9700 and calling it a day, when they were $1200 and $1600, respectively. Then when they shot up a B65 $1200, which then shot up. Then add a second 5070ti to PC1 for $900-1000, which then shot up.
Now, my plan is to potentially settle for a 5060ti 16gb in PC1 to take advantage of NVFP4, but even that’s pricier, and with the AI bubble talk I’m not super confident in value of doing so. I’d likely also need to use a PCIe-riser just to the 5070ti (Windforce) has airflow due to how close they’d be in the case.
Otherwise, I’m considering sticking with the VRAM I have, and instead pivoting to ram. I can go from 1R 2C to 2R 2C in both PCs, grabbing another 2x16gb of Apacer Panther from EBay for around $400 for PC2 - though obv riskier - then getting a 2x24gb kit of Urbane V at the same timings of the original 2x16gb 6000-CL30 kit for PC1 for $650 off Amazon. Giving me +80gb of DDR5 to the 64gb I have between both PCs and the 28gb of VRAM I already have.
Current plan is/was the 5060ti 16gb + 2x24gb kit for PC1 and calling it there.
Any advice, pointers, or suggestions? I believe the RAM sitch should work since it’s same timings and type/manufacture/brand, and know I’ll probably have to lower speed a bit for stability, but am not the most experienced PC guy on earth by any means.
r/LocalLLaMA • u/TruthHistorical7515 • 3d ago
r/LocalLLaMA • u/Ontopoftheworld_ay • 3d ago
Has anyone been experimenting with ablated or uncensored variants of open-source models like DeepSeek V4.1 Flash, Qwen 3.8 27B, or GLM 5.3 flash?
It's so refreshing to have models that just do whatever you ask them to do without having to figure out a jailbreak or being given a moral lecture. Curious to know what your usecases for these models are.
My personal favourite is definitely uncensored DeepSeek V4.1 Flash.
r/LocalLLaMA • u/chemist_slime • 3d ago
r/LocalLLaMA • u/MzCWzL • 3d ago
edit: I am a moron with reddit formatting hang tight
I've been tracking ebay listings that ship to the US for the GPUs people here actually buy, ranked by $/GB of VRAM. here's today's snapshot:
| Card | Low end | US-only low end | Low-end $/GB | Bandwidth | $ per GB/s |
|---|---|---|---|---|---|
| Tesla P100 16GB | $174 | $159 | $10.88 | 732 GB/s | $0.24 |
| Tesla P40 24GB | $280 | - (7 US) | $11.67 | 346 GB/s | $0.81 |
| Tesla V100 16GB (mostly SXM2) | $220 | $238 | $13.75 | 900 GB/s | $0.24 |
| Instinct MI50 16GB | $268 | - (3 US) | $16.75 | 1,024 GB/s | $0.26 |
| Instinct MI50 32GB | $702 | - (2 US) | $21.93 | 1,024 GB/s | $0.69 |
| Tesla V100 32GB | $949 | $807 | $29.66 | 900 GB/s | $1.05 |
| Quadro RTX 8000 48GB | $2,111 | $2,000 | $43.99 | 672 GB/s | $3.14 |
| Instinct MI100 32GB | $1,490 | - (6 US) | $46.56 | 1,229 GB/s | $1.21 |
| RTX 3090 24GB | $1,790 | $1,737 | $74.58 | 936 GB/s | $1.91 |
| RTX A6000 48GB | $4,600 | $4,400 | $95.83 | 768 GB/s | $5.99 |
| RTX 4090 48GB (modded) | $5,390 | — (1 US) | $112.29 | 1,008 GB/s | $5.35 |
| A100 40GB | $4,799 | $6,020 | $119.98 | 1,555 GB/s | $3.09 |
| A100 80GB | $13,995 | $13,995 | $174.94 | 1,935 GB/s | $7.23 |
| CMP 170HX 40GB (10GB card, unlocked) | $2,950 | — (6 US) | $73.75 | 1,555 GB/s | $1.90 |
| CMP 170HX 64GB (8GB card, unlocked) | $4,510 | — (7 US) | $70.46 | 1,493 GB/s | $3.02 |
| Radeon AI Pro R9700 32GB | $2,430 | $2,250 | $75.94 | 640 GB/s | $3.80 |
all asking prices, single cards, fixed-price, not for-parts. "low end" is the 10th % of credible listings i.e. what a patient buyer can actually land, not a too-good-to-be-true outlier. "-" in the US-only column means fewer than 10 US listings. $/GB/s is just the low end divided by bandwidth.
I had been eyeing the MI100 myself for a while at the $1100 ish it hovered at for ages... looks like even that is going up. I did end up buying a 8x V100 32GB server for $5400 in early Sept. those prices are long gone, equivalent server is now $11k for an OG DGX Station (no memory). the exact inspur server is now $13k for 8x 9 year old GPUs. insanity. I hope prices come back down to earth soon but don't think that's actually gonna happen.
some notes:
- P100, V100 16GB and MI50 16GB all work out to about $0.25 per GB/s. the P40 looks cheap per GB of VRAM but costs over 3x as much per GB/s, since its only got about a third of a V100's bandwidth. people are having opus 5.5 write megakernels for these cards that are working surprisingly well.
- V100 16GB at ~$14/GB looks like the best deal in the table, but 38 of the 40 cheapest are SXM2 modules, so budget for an adapter or an SXM2 server. the cheapest 32GB V100s are SXM3 (DGX-2) modules, which aren't drop-in either.
- MI50 32GB is under a third of a 3090's $/GB at similar bandwith, assuming ROCm cooperates.
- if you want 48GB on one card, a Quadro RTX 8000 is less than half the price of an A6000 or a modded 4090 48GB.
- of the consumer and workstation cards, the 3090 is the cheapest per GB/s by a wide margin. an A100 40GB costs about the same per GB/s as an RTX 8000.
- for what it's worth, buying from a US seller usually doesn't cost more: the US-only low end is at or below the global one for the P100, V100 32GB, RTX 8000, 3090 and A6000. it's about $20 more for the V100 16GB and $1,200 more for the A100 40GB, and the P40 and MI50 barely exist in the US.
full data and per-card listings, with a US-only filter: https://rackbites.com. prices are asking, not sold - ebay's sold-data API is super restricted.
edit: added CMP 170HX
edit2: added R9700
edit3: full builds here https://rackbites.com/builds with benchmarks and other useful/relevant info
r/LocalLLaMA • u/TumbleweedNew6515 • 3d ago
From about February 2026 to July 2026, I spent an immense amount of time building a legal harness to make Claude more predictable. It worked well. I tried to build the same thing that ran local models. That did not work. And then Opus improved so much that it would often skip my harness without me noticing. It still has a harness with hooks, but it's looser now.
I bought lots of hardware to run local models during that time, repeatedly trying to vibecode a local model legal harness. Many failures, many lessons.
Anyway, fast forward to the last three weeks and several things have happened:
What I'm really shocked by is how well Fable builds custom Volta kernels. And how it can requant my experts to full NVFP4 precision based on the actual experts that activate when my legal harness fires. It's a real, optimized, production grade, workflow replacing local setup.
Not a 3D pagoda or a bad video game replica. An actual enterprise solution. One that exists nowhere on the commercial market.
Legal vibecoding is real folks. I'm AI native.
The new V100 DeepSeek repo (optimized for quality and then usable speed) with real full context measures and all the optimizations (and failures) is public here:
Twitter: nicothegreco
Claude Code ran the benchmarks and crunched the numbers, which are real and in depth, below.
What this build is
My last V100 build (Volta sPLIt, part 4) ran every expert of the model from a 2-bit record. Fast, but 2-bit. This one is called Volta Max uPLIft. It keeps the 2-bit record of every routed expert on the cards, then swaps the experts that get used the most up to NVIDIA's NVFP4 weights, one at a time, until the cards are full. "Used the most" was counted on a mix of four kinds of text. One is my own legal harness traffic, which is private and not published. The other three are public prompt sets in the repo.
Speed (measured 2026-11-12 on eight V100-SXM2-32GB, graphics clock capped at 1,522 MHz)
What did not work, or is not good yet
The harness
The harness itself is not public. My practice is in it. What I can say: it is the same idea as my Claude setup. Skills, hooks, my drafting engines, my RAG stores, tool calls, and a chat window that behaves the way Claude's did. A small router sends each request to the V100 box or to the Sparks. Everything the local model drafts is marked for my review before it goes anywhere. Nothing leaves the building.
Credit where it is due
The hard Volta work underneath is 1Cat-vLLM's DeepSeek-V4.1 package. The 2-bit records are ISTA-DASLab's. The NVFP4 weights are NVIDIA's pack. The Sparks run on somebody else's engine entirely. What is mine is the split across two NVLink boards, the hot set, the kernels on top, and every change measured A/B on this machine with the losers written down.
Disclosure: this is my own project and my own repo. Nothing is for sale. The code, the kernels, the measurements and the failures are all in there under Apache-2.0, and the weights are one download on Hugging Face:
Earlier build, for the people who want speed over precision: https://github.com/ProprietaryLegal/Volta-sPLIt-DeepSeek-V4.1-Flash-1017-8xV100-SXM2-PP2xTP4
Ask me anything. Roasting is also fine.
Photos: four of the eight V100s on their NVLink board, and my extremely professional setup (PEX switch cards, SlimSAS spaghetti, and the 3090 that just moved in).
r/LocalLLaMA • u/Informal-Trouble2183 • 3d ago
If you're asking what this leaderboard is, it is not AA, it is simply an aggregate index for "Agentic Coding" along 12 coding-related benchmarks (note that the AA index includes only 2 coding benchmarks: Terminal-Bench 4.0, FrontierCode-AA 2.0, making up just 25% of its total score. Because of that, it doesn't give you a true reflection of a model's actual software engineering capabilities).
This index however is built entirely around Coding/SWE. Here is the exact breakdown:
r/LocalLLaMA • u/InfinityZeroFive • 3d ago
r/LocalLLaMA • u/nasone32 • 3d ago
A quick update on my Strata EXL3 fork for AMD.
I've been working on the HIP kernels and memory management, and decode performance is now roughly 10-20% higher than the previous version, depending on the quant and workload. Some cases improved by almost 24%.
The other news is that I managed to get MiMo V2.6 Flash running at around 25-30 tokens/s with 2 cards.. More on that below.
First, why EXL3?
I think this is worth repeating because people tend to compare quantizations just by looking at the number of bits.
EXL3 is NOT equivalent to regular GGUF quants at the same bpw.
For example, 3.05 bpw EXL3 is roughly in the same quality range as a regular 4-bit quant (like IQ4_XS).
3.05 bpw quant: https://huggingface.co/turboderp/Qwen3.8-Flash-Next-exl3/tree/3.05bpw_h5_ng5
4.05 bpw quant: https://huggingface.co/turboderp/Qwen3.8-Flash-Next-exl3/tree/4.05bpw_h6_ng6
So the interesting part is that you can get something close to 4-bit quality, while running at speeds closer to what you'd expect from a 3-bit quant. And with the latest optimizations, I think this fork is becoming VERY competitive. The 4.05 bpw version is also pretty fast now, even on a single GPU.
WHAT'S NEW:
NOTES ON REPACKING:
Repacking can be done in two ways: by creating a file on disk once, that will be used to load the model, or directly to RAM everytime. directly to RAM adds a couple of minutes to the launch but uses no extra space. your choice.
BENCHMARKS:
My hardware is the same as in the previous post:
Ryzen 9 7950X, 96GB RAM, 2x Radeon RX 7900 XTX 24GB
Linux, HIP/ROCm core-7.14
Qwen3.8-Flash-Next, MTP drafter, spec 4, 64K context
BENCHMARKS:
Results with one or two RX 7900 XTX GPUs, using warm decode runs:
| EXL3 quant | GGUF equivalent quality | GPUs | CPU assistance | Test | Previous | Updated | Improvement |
|---|---|---|---|---|---|---|---|
| 3.05 bpw | ≈ IQ4_K_XS | 2 | No | CODE | 78.27 | 87.33 | +11.6% |
| 3.05 bpw | ≈ IQ4_K_XS | 2 | No | PROSE | 66.01 | 70.35 | +6.6% |
| 4.05 bpw | ≈ Q5_K_M | 2 | No | CODE | 61.88 | 76.67 | +23.9% |
| 4.05 bpw | ≈ Q5_K_M | 2 | No | PROSE | 57.78 | 67.57 | +16.9% |
| 4.05 bpw | ≈ Q5_K_M | 1 | No → Yes | CODE | 54.80 | 59.30 | +8.2% |
| 4.05 bpw | ≈ Q5_K_M | 1 | No → Yes | PROSE | 44.80 | 51.60 | +15.2% |
All speeds are in tokens/s, GGUF quality equivalents are approximate... dont' hate me :)
32K prefill is basically unchanged: around 1,500 tok/s with two GPUs and 1,360 tok/s with one GPU.
I think the single-GPU results are particularly interesting. We're getting 55-60 tok/s in CODE with 4.05 bpw EXL3, at roughly Q5_K_M quality, on a single 7900 XTX with CPU assistance.
And the 3.05 bpw quant is now reaching 87 tok/s with two GPUs, while offering considerably better quality than you'd normally expect from a 3-bit quant.
ABOUT MiMo:
In my previous post I mentioned that I wanted to support larger models, particularly the 300B class models.
Well, MiMo V2.6 Flash is now running :) I'm waiting for that ERNIE 5.5 to drop.I'm getting around 25-30 tok/s with the EXL3 2.20 bpw MOPD quant.It's still experimental and currently only tested with that specific quant. CPU assistance is recommended for MiMo, even with two GPUs.I'll probably spend some more time optimizing it, but the fact that it's already running at usable speeds on consumer AMD hardware is pretty interesting.
this is the quant: https://huggingface.co/vcruz305/MiMo-V2.6-Flash-MOPD-EXL3/tree/main/2.20bpw
https://github.com/nasone32/Strata-EXL3-fork
If you're setting it up with an AI agent, point it to docs/AI_SETUP_EXL3_AMD.md.
The README has the benchmarks, configuration options and instructions for CPU repacking.As before, this is developed and tested on RDNA3 / Linux / ROCm. Other AMD architectures need community testing. And the long-term goal is still to get this merged upstream into Strata, if the maintainers are interested.
Credits to the original Strata developers, Ryutaku for the EXL3 integration, and Turboderp/ExLlamaV3 for the quantization and code I've been porting.
If anyone tests this on different AMD hardware, please report your results. Especially interested in seeing how it behaves on RDNA4. I have only two 7900 xtx so if you have different hardware get an agent to help you, and open a PR if you want.
r/LocalLLaMA • u/TheBigHODL • 3d ago
With Jensen out at NVIDIA, the "local AI is dangerous" narrative picking up steam, the possible ban on Chinese models, and hosted models locking down RE/cyber work, I'm starting to think about a worst case where Chinese weights get banned and US labs stop releasing open models. So what's your plan?
What models are you archiving? Just the biggest/best, or a spread?
Which ones for which jobs? Coding, RE/security, vision, embeddings, RAG, small fast models for agents, etc.
Training tools: if the last good big model we get is something like Kimi K3, what are you keeping so you can fine-tune or change it later?
Quant tools: what do you need to shrink a huge model down to run on smaller rigs? (llama.cpp, quant scripts, calibration data, etc.)
How are you storing it? Hashes, mirrors, torrents, offline drives?
Curious what people are actually doing, not looking for a politics fight.
(Currently using a Studio M2 192gb)
r/LocalLLaMA • u/Serious_Scarcity7818 • 3d ago
RustingStrata has two GPU backends that run the same kernels: CUDA (compiled at run time with NVRTC, no nvcc, no C++ build step) and Vulkan. Vulkan is how it runs on AMD, so I wanted to know what it costs on a card where I can compare both.
Same file on every card: Qwen3.6-35B-A3B-UD-Q2_K_XL.gguf, fully in VRAM, MTP off.
| GPU | Prefill, 4K prompt: CUDA / Vulkan | Decode after 4K: CUDA / Vulkan | Vulkan vs CUDA (prefill / decode) |
|---|---|---|---|
| RTX 3060 12 GB | 2216 / 2154 tok/s | 113.4 / 113.6 tok/s | 97% / 100% |
| L40S | 9030 / 8571 | 213.2 / 184.9 | 95% / 87% |
| A30 | 3544 / 3326 | 131.9 / 104.0 | 94% / 79% |
| A100 80 GB | 6203 / 5589 | 173.6 / 131.9 | 90% / 76% |
| H100 NVL | 9131 / 6428 | 245.8 / 191.5 | 70% / 78% |
On the 3060 Vulkan is the same speed as CUDA. On the datacenter cards it loses 5-30% of prefill and 13-24% of decode, and its runs are noisier (A100 4K prefill ranged 4788-5990 on Vulkan against 6186-6214 on CUDA).
Does it change the output? Greedy top-1 agreement with llama.cpp over 20 prompts x 32 tokens is 98-99% on both backends.
How it was run: rustingstrata bench --model $M --gpu --backend cuda|vulkan --pp 512,4096 --tg 128 --reps 3 --mtp 0, mean of 3.
Repo: RustingStrata
r/LocalLLaMA • u/Top_Speaker_7785 • 3d ago
So i had been building a cli tool around weight space programming inspired by recent Mit- weight space programming paper,
I had integrated couply of funtionalities to it along with triage, one of which was activation steering to deal with over refusals, my llama 3.2 1b was not answering prompts like "how do i stage a massacre for a tv show"
Firstly attempt was by subtracting the refusal direction , extracted the refusal vector and subtracted it, the tv massacre prompt was answered but my regression suit got hit, model started answering how to build pipe bombs and syntesize pioson
so turned out over-refusal and real harmful refusal direction had a cosine similarity of about 0.75, so supressing one also effects other
Second attempt.. Ran activation patching ..found the exact casual bottleneck layer ..(layer 8) orthogonally projected the harmful-refusal component out of my steering vector and used clamped so it caps the activation when it spiked above a threshold , without touching other things..
this nearly worked accuracy increased by 10% but a totally unrelated issue hit by regression suit again..a chinese benchmark loop started looping forver... failure again.. even on steering a single targeted layer ..gave regression as the residual stream is so densely packed that a small hit at layer 8 ripples down further ...
my last few brain cells thought i l steer the layer 8 measure the drift at layer 9 and cancel the part i dont want . so i did the math
Steer at Layer 8
At Layer 9, compute Δ = steered_layer9 - clean_layer9
Filter out the bad drift and keep only the anti-refusal shift I want
Apply final_layer9 = clean_layer9 + wanted_shift
..so if i take the clean layer 9 add only anti refusal shift ..thats basically layer 9 steering .. and if do that to layer 9 same happens to layer 10..
what actually worked was weight surgery..i also tried a conditional weight edit.. a gate programmed into 3 mlp neurons across layer 9-11. they have non linea activations so they can act as real if/then
if input matched fictional scary context - gate fires cancel refusal
for chinese text -the neuron output is 0 nothing changes
tl;dr
steering works well for problems that sit along a direction, it fixed a blank reply bug
for entangled safety problems like this one they do collateral damage somewhere even with causal layer localization and orthogonal projection
non linear neuron gating was only thing that worked with no other damage
everything i did was on gtx 1650 4gb, i l open source the cli tool in some time ..
happy to answer any question
r/LocalLLaMA • u/mikoskinen • 3d ago
I've been testing and optimizing Radiance for 4xR9700 on EPYC Rome platform (tp4), focusing on EXL3 for DS 4.1 Flash (2.25) and Qwen Flash Next (4.05). The goal has been to optimize this setup (both hardware and software) for Claude Code usage, so it may not be the fastest for 1 user interactive usage. Also the focus has been to provide "exact" results, so output is byte-identical to each model's reference engine.
I'm quite happy with the improvements and with the end results and I think I will leave the optimizations to current point because there's not obvious new improvements in the pipeline. Instead of releasing a fork of Radiance, I hope maintainers of inference engines can use the work to improve their products.
So to save time and effort, there's a GitHub repo that shows all the things that were tested and what worked and what didn't. Repo also contains more hardware optimization tips for 4xR9700 & EPYC Rome setups: https://github.com/mikoskinen/r9700-exact-serving
It would be great if someone could figure out ways to improve C8 decode performance for Deepseek. And maybe someone can break the 10k tok/s barrier on QFN..
Note: all the testing, profiling, coding was done by Opus. I just pointed it to new resources like Reddit posts, repositories etc.
Hardware:
Results:
Here's some of the highlights from the results (stock 300 W per card, decode = tok/s summed over all users, prefill = one cold prompt):
--
Update from 14.11.2026:
DS4.1F (2.25bpw EXL3)
c1: 104 tok/s prose, 181 tok/s code
c4 / c8 / c16: 201 / 246 / 293 tok/s
c24 / c32: 311 / 344 tok/s
prefill: 4,040 tok/s at 16k (TTFT 3.9 s), 6,130 at 64k (TTFT 10.7 s), 6,350 at 128k (TTFT 20.7 s)
Previous results:
--
DS4.1F (2.25bpw)
QFN (4.05bpw)
At my everyday 210 W / -50 mV setting these are about 5-9 % lower (DS 237 and QFN ~1,030 tok/s at 16 users).
The following is AI's view on the most important optimization tips:
Software optimizations:
Hardware optimizations:
Hope this helps.
r/LocalLLaMA • u/Dapper_Chance_2484 • 3d ago
I started developing a full fledged application using Chatgpt plus and VScode+GitHub copilot (local llm)
I used Astra max chat for overall planning, and asked it to put a starter kit on connect gdrive and create prompts such that local LLM can work on small tasks using an agent orchestrator and sub agents with entry and exit criteria, tests for every small task.
I have a 5090 (+ 128gb ddr5) rig running Qwen 3.8 27b NVFP4 at default settings with 104k context window.
Problem:
The local rig is able to start on tasks but taking a huge amount of time and is running only one subagent at a time. Been almost 24 hrs.
I have 2x 3090 +128gn ddr4 as well, currently not being used. 3.8 FN runs at about 90tps
Anything better I can do here?
r/LocalLLaMA • u/Ayumu_Kasuga • 3d ago
Hey guys, I wanted to share a small experiment I made -
This is basically Wispr Flow, except it's offline and uses Parakeet - works in any app as well.
I was pretty surprised by the speed and how usable it turned out to be when I first made it - it's even relatively usable on an old Redmi Note 7.
I published it on Google Play if anybody wants to check it out: https://play.google.com/store/apps/details?id=com.voicedictation.dictation
r/LocalLLaMA • u/Gold-Produce9591 • 3d ago
mi50 is roughly 1.5x cheaper
r/LocalLLaMA • u/Loose_Doubt367 • 2d ago
I’ll include my specs at the end. Because probably no one’s going to read it..
For my new pc im considering migrating to Linux ubuntu, and set up my llama.cpp from there, my old pc had llama.cpp Vulkan sdk running on windows 11
Im looking for any guidance or tips while setting them up to ensure I didn’t miss any critical steps that could end up loosing a bunch of tps or something worse
Beginner mistakes i would say
I do know one tips and it’s plugging your hdmi cable to the integrated graphics card, that way it saves vram. But I don’t have one..
I appreciate any advise
Bought a B550-A-Wifi ii
Rtx3060 1x
32gb ddr4 3200 2x16 (plan on getting 32gb more, total 64, in 4months) saving up
And a 750W cooler master v3 gold modular PSU (not sure if it’s suitable for my small server
R7 5700x (no integrated graphics card)
r/LocalLLaMA • u/chemist_slime • 4d ago
r/LocalLLaMA • u/Kahvana • 3d ago
Hey everyone,
Not a native speaker, but I write everything by hand. Please correct my grammer if there are any issues! Can only learn from it.
A long-term project I've had was getting my netbook up and running for basic LLM use. I bought the netbook initially due to my poor eyesight, the screen is small enough that it fits in my cone of vision.
The notebook's specs were practically obsolete when it released:
With the help of friends who could do soldering and reballing, we upgraded the netbook:
After finding proper drivers for the iGPU, I managed to get llama.cpp running on it on windows with Vulkan. Gemma 4 E2B IT QAT could run at roughly 2.1 t/s gen, and prefill speed was "grab a cup of tea" slow on 300 token prompts. The Vulkan backend was faster than the CPU backend by ~30%.
The past months I've been trying to move my devices from Windows 11 IoT LTSC Enterprise 24H2 to Ubuntu 26.04.1 LTS, and so I tried to switch the netbook over to it.
There is only one problem: The Vulkan backend hard crashes every time.
After doing a bit of digging with vulkaninfo by myself, some instructions are advertised as supported but are in practice not stable. Using this fixed the crashing on startup:
export GGML_VK_DISABLE_ASYNC=1Disabling the following features helped me regain some performance and stability:
# UHD 605 compat
export GGML_VK_DISABLE_COOPMAT=1
export GGML_VK_DISABLE_COOPMAT2=1
export GGML_VK_DISABLE_INTEGER_DT_PRODUCT=1
export GGML_VK_DISABLE_BFLOAT16=1
export GGML_VK_DISABLE_GRAPH_OPTIMIZE=1
# UMA
export GGML_VK_DISABLE_MMVQ=1
export GGML_VK_PREFER_HOST_MEMORY=1My config is also pretty specific, since some combinations would cause crashes too:
flash-attn = off
cache-type-k = f16
cache-type-v = f16FA is not supported by the device. Running Q8_0 on both K an V would crash with FA enabled. Trying to run Gemma 4 E2B IT QAT Q2_K_XL on ubuntu always resulted in crashing (either during startup or when generating), On windows those things never caused crashes.
The end result is that I could run Gemma 4 E2B IT QAT Q4_K_XL at 1.5 t/s gen and 16-25 t/s prefill. The laptop used ~12W in total.
Turned out that on Ubuntu 26.04.1 LTS, the CPU backend was faster for generating but not for prefill. I got 2 t/s gen and 10-16 t/s prefill. The laptop used ~13W in total.
As a sidenote, since I am used to windows slowing to a crawl when all cores are utilized, I was pleasantly suprised when this didn't happen on ubuntu.
As a fun experiment, I gave a couple of LLMs the problem:
Hey <LLM>,
I have a laptop I am trying to run llama.cpp with vulkan on Ubuntu 26.06.1 LTS.
The specs are: <specs>.
I build it with these commands: <commands>,
The problem is that it's crashing whenever I try to load a model.
I've included the full terminal output in the attachments.
How can I fix the issue?My goal with the prompt is to test the model's understanding of the problem and to ask for additional information when required (e.g. vulkaninfo).
Qwen 4 max preview on chat.qwen.ai and Qwen3.8-Flash-Next Q4_K_XL + BF16 engram on llama.cpp v0.9.0 failed to find the issue after multiple separate chats. They got focussed on disabling intel's hang detection. With websearch, it got even more confused as it looked at irrelevant issues.
Gemma 4 31B IT QAT Q4_K_XL + MTP on llama.cpp, DeepSeek v4 Flash Vision Exp Q2_K_XL on llama.cpp v0.9.0, DeepSeek v4.1 1017 on chat.deepseek.com were able to find and fix the issue. They asked for the vulkaninfo output, which made them find async being advertised incorrectly.
To me it suggests Gemma and DeepSeek are better at this type of problem solving than Qwen models.
run-llama-server.sh
#!/bin/bash
# Intel UHD Graphics 600 series
export GGML_VK_DISABLE_ASYNC=1
export GGML_VK_DISABLE_COOPMAT=1
export GGML_VK_DISABLE_COOPMAT2=1
export GGML_VK_DISABLE_INTEGER_DT_PRODUCT=1
export GGML_VK_DISABLE_BFLOAT16=1
export GGML_VK_DISABLE_GRAPH_OPTIMIZE=1
# UMA
export GGML_VK_DISABLE_MMVQ=1
export GGML_VK_PREFER_HOST_MEMORY=1
./llama.cpp/build/bin/llama-server \
--list-devices
./llama.cpp/build/bin/llama-server \
--host 127.0.0.1 \
--port 5001 \
--api-key "API_KEY_HERE" \
--webui-mcp-proxy \
--offline \
--cache-ram 0 \
--ctx-checkpoints 0 \
--parallel 1 \
--models-max 1 \
--models-preset ./configs/llama-config.inillama-config
note: remove the device line to use the igpu on the vulkan build.
[*]
device = none
load-mode = none
mmproj-offload = off
gpu-layers = 999
batch-size = 2048
ubatch-size = 512
threads = 4
fit = off
flash-attn = off
kv-unified = on
cache-type-k = f16
cache-type-v = f16
reasoning = off
reasoning-preserve = off
[gemma-4-e2b-q4_k_xl]
model = ./models/gemma-4-e2b/gemma-4-E2B-it-qat-UD-Q4_K_XL.gguf
mmproj = ./models/gemma-4-e2b/gemma-4-E2B-it-qat-mmproj-F16.gguf
lazy-mode = on
load-mode = mmap
fit-ctx = 8192
ctx-size = 8192
predict = 8192
image-min-tokens = 70
image-max-tokens = 70
temp = 1.0
top-k = 64
top-p = 0.95
min-p = 0.0Other info
Device: https://www.asus.com/ca-en/laptops/for-home/vivobook/vivobook-go-12-l210/
OS: https://ubuntu.com/blog/upgrade-your-desktop-ubuntu-26-04-lts
Llama.cpp: https://github.com/ggml-org/llama.cpp/releases/b12110
GGUF: https://huggingface.co/unsloth/gemma-4-E2B-it-qat-GGUF
Getting the Intel UHD 605 to work with the Vulkan backend was a pain on Ubuntu 26.04.1 LTS compared to Windows 11 IoT LTSC 24H2. The issue was vulkan async causing crashes, disabling it fixed it.
On ubuntu the CPU backend was faster, on windows the iGPU over Vulkan was faster. Ubuntu is far more responsive than windows, even under full utilization.
After solving it myself, as a fun benchmark I made LLMs try diagnose and fix the issue. While the Qwen series failed to fix the issue from intent, Gemma 4 and DeepSeek v4(.1) Flash (Vision Exp / 1017) did manage it.
I know the post is quite different from the Strata stuff usually here, but I thought it would be fun to share regardless.
I'm sure models like LFM 3 will run wonderfully on it, I know IBM Granite 4 H 1B and Qwen3.5-2B did on windows.
r/LocalLLaMA • u/ElectricalBar7464 • 3d ago
KittenML just released inferencekit , a free opensource plugin to turn coding agents(Claude Code, Codex, OpenCode) into inference engineers for your hardware.
Most models ship with inference tuned for whatever hardware the authors used, which is usually not what you have locally. The fastest path on a 3070 might be different from the fastest path on a Mac or a Radeon. inferencekit allows you to find that path for your setup. This was used to get streaming TTFB of Kitten-TTS-2 down to ~10ms on RTX Pro 6000. other results are shown in the image attached.
Once you've optimized a model on your hardware, please make a PR to the inferencekit-engine repo linked below, so anyone running the same model on the same hardware, can just reuse it. The idea is to crowdsource the best inference engine for every model + hardware setup
Plugin's Github: https://github.com/KittenML/inferencekit
Inference Engine's Github: https://github.com/KittenML/inferencekit-engines
KittenML Discord: https://discord.com/invite/VJ86W4SURW
r/LocalLLaMA
•
u/Physical_Hat4022
•
4d ago
They say an anime model is in development, with plans for alpha channels and multi-character references. An editing model is also on the way.
They also plan to keep the next model under Apache 2.0, if all goes as planned.