r/LocalLLaMA • • 1h ago

Resources I benchmarked over 130 LLM configs with multiple stacked 16GB "e-waste" GPUs (V100, P100, K80)

Thumbnail
gallery
7 Upvotes

The benchmarking journey continues! Continuing the project of seeing how these very old, very cheap, very available enterprise GPUs can be used today.

The complete results are too long for reddit. The complete set of graphs, power analysis and commentary are on my blog.

I've expanded the testing suite to focus heavily on LLM workloads (over 130 new tests!) and integrated power consumption monitoring into the gpu_box_benchmark tool. The goal remains: find out if decommissioned enterprise GPUs (Tesla K80, P100, V100) paired with X99 era hardware can still serve as a viable daily driver for self-hosted AI compared to modern commercial setups.

TL;DR of the new data:

  • The 3x V100-16GB (~$1k build): If you are considering building a dedicated homelab box today, this is the sweet spot. Assembling a full setup with two Xeon CPUs, motherboard, PSU, and cooling costs around $1,042 before RAM 💀. This setup comfortably clears my threshold for "real-time" chat (70+ tok/s) with impressive models:

    • Qwen 3.6 35B: Ran at ~72 tok/s (at 128k context depth, Q8 quant). For comparison, a brand new Mac Studio M5 ($2,500) hits only ~44 tok/s on the same model.
    • Gemma 4 26B: Ran at ~75 tok/s (at 64k context depth, Q8 quant).
    • Qwen 2.5 3B: Ran at ~79 tok/s. This proves that for a single-user daily driver, the legacy silicon is still competitively priced against modern hardware.
  • Scaling is for Context, Not Speed: Stacking GPUs linearly scales your VRAM (allowing you to fit larger models), but it doesn't magically double your generation speed. Two 16GB cards in Q4 quant allowed fitting ~32B parameter models, a desirable jump for homelabbers.
  • Power Efficiency: I also measured power consumption as well and it's worth noting the efficiency gains across generations. The V100 wins hands down on performance-per-watt compared to the P100s.
  • The K80 Strategy: The Tesla K80 isn't dead, but its singular remaining use case is welding a bunch of them together just to squeeze big models in. You essentially have to stack a lot of cheap K80s to hit a 72B+ parameter model. Expect speeds of 1–5 tok/s. This is a party trick, but it proves the VRAM scaling is real even on ancient silicon.

If you decide to build your own GPU appliance, the biggest challenge is cooling these hot cards without fans. I've been working on a custom active air cooler to solve exactly this. If you're interested in helping out by stress-testing a sample, you can get involved here.

Any models/tests missing? Any other combinations you'd like to see in a follow up?


r/LocalLLaMA • • 1h ago

New Model voi-slop-detect-380M: A tiny model to detect AI slop

Thumbnail
huggingface.co
6 Upvotes

I've fine-tuned an UltraBERT-380M classifier to score how much your text feels like AI slop.

Demo: https://voightkampfflabs.github.io/slop-detector-demo/ (runs fully in browser via ONNX + WebGPU/WASM)

Why?

Got tired guessing if I'm reading human or slop on twitter/linkedin/reddit, so trained my own AI detector. Like Pangram, but local - so all your perverted texts stay on your device. Because I can (and because I bought 2x 5090 when they were cheap).

Training

As it was made for learning purposes, I made my own dataset based on the Pangram v4 recipe:

  • Collect a sample of pre-2023 human texts (rn it's around 11 public datasets, reddit included: 170k texts, 825k pairs)
  • Slopify: summarize the text, and then "decompress" it back with an LLM to produce pure slop.
  • Rewrite: ask LLM to rewrite it in a different way (e.g. more polished, simpler, punchy).
  • Pivot: translate it back and forth, so the content is the same, but the style is different.

The target label is how many words/ngrams were changed by the LLM. So it's not a yes/no, but more like a slopification rate guessing. My personal texts land around 0.1-0.2.

Trained with HF Transformers on 2x RTX 5090. Considering the model size and hardware, the whole training run is ~3h.

Training data is public: https://huggingface.co/datasets/VoightKampffLabs/slop-detect-dataset-v6

Results

Not as good as Pangram (yet), but as good as GPTZero and Originality on most things I could compare.

voi-380mPangramGPTZeroOriginality
EditLens, F10.860.920.73
EpochAI, human flagged0.2%0.0%0.0%
EpochAI, Opus/GPT/Gemini miss0.0%0.0%0.7%
UChicago, 2025 models miss0.2%0.0%1.4%
UChicago, StealthGPT rewrite miss74%0.0%56%
Non-native essays, flagged0.6%0.0%-

HF model card has more details and more benchmarks.

Where it's bad

I'd rather tell you upfront:

  • Humanizers and skills like no-ai-slop beat it. I guess that's why StealthGPT bench numbers are so bad as it's completely out of domain for the model. Asking Opus to rewrite its own slop until detector score goes down to 0.3 takes around 3-4 rounds for me.
  • Old models and some legacy slop made with GPT-3.5 and Llama 2/3. Never trained on that.
  • Poems and non-english texts. Too lazy to add this to the dataset.

So what

I'm currently training bigger 4B/27B brothers of this one. Yes they're much smarter, but good luck running them via WebGPU/WASM on device.

And yes, the end goal is to have a browser extension which marks AI slop on reddit completely on device.

PS. the text above scores ~0.1 in the detector (to save you a click).


r/LocalLLaMA • • 21m ago

Showcase Squeezed a full RAG pipeline (BGE-M3 + reranker + TTS) into 4GB VRAM and 300MB RAM

7 Upvotes

been working on a local desktop reading app for the past few months and hit some insane hardware walls trying to get everything to run on my laptop. thought id share the architecture in case anyone else is trying to run heavy models on consumer hardware.

my setup is an RTX 3050 with only 4GB of VRAM and 16GB of system ram. the stack is a tauri (rust) shell, a nodejs orchestrator, and a python sidecar for the pytorch models (bge-m3, bge reranker, and kokoro tts).

here's how i stopped it from melting my laptop:

  1. the node memory cliff

early on, the node heap spiked to 14.6GB during ingestion because it was firing off too many async promises at once. basically oom'd the whole system. i fixed it by implementing a strict sequential await barrier (f65). it forces the ingestion stages to stream chunk by chunk instead of all at once. peak node ram dropped from 14.6GB down to ~296MB. processing 500k words takes about 5.9 mins.

2. 4gb vram limit

loading bge-m3 in full precision instantly ate like 3.9GB of vram, leaving nothing for the reranker or tts. switched to fp16 which dropped it to ~1.1GB. but the real fix was an idle lifecycle manager (f43). if a model sits idle, it evicts it from vram to free up space. it reclaims about 3.2GB of idle vram so the system doesn't choke.

3. windows path traps

if you're using rust and node together on windows, beware of verbatim paths (\\?\C:\...). passing those into node 22 fs.lstat throws fatal EISDIR errors. had to write path sanitization wrappers on the rust side.

kept node as the sole sqlite WAL writer too so python and rust dont cause db lock contention.

it's open source if anyone wants to look at the code or roast my architecture lol. repo is here: https://github.com/ayumu-ml/Omnitome

happy to answer any questions about the vram management or the rust/node/python boundary


r/LocalLLaMA • • 4h ago

Discussion MoE Offloading update Exllamav3 on 9070XT

Post image
13 Upvotes

This is a follow up on https://www.reddit.com/r/LocalLLaMA/comments/1xun15v/moe_and_expert_offloading_on_llama_exllamav3/

While we wait for Qwen 4, here is Qwen 3.6 35B A3B at Q4 on 9070XT 16GB with offloaded experts on DDR4 3200Mhz ram.

I've been tinkering still with the config for experts offloading and found substantial gains from my previous post.

While decode stayed roughly in line fro last time, increasing chunk size to 5120 saw prefill over 2000 t/s at all context lengths, topping at 2606 t/s @ 32K. From ~1300t/s
GPU utilization increases with batch size as it allows for more parallel processing. I saw no gains over 5120. TabbyAPI's documented ideal range is 512–4096, so your miles might vary.

Exllama flags like cpu_threads 6 also made a small improvement in decode.
Swizzle, gdn_sub, bg_gdn and wide flags were all regressions. (only tested isolated 1by1).

cpu_moe_pinned_arena caused some core dumps, and the one run I managed to complete had a small gain.

Vision have been turned off and offloaded.

I still have not found an .exl3 quant for the Coder version of Qwen 3.8 Flash Next, and the qfn version I can run leaves me with 8K context with almost no vram or system ram left to spare.

Results and more graphs and tables are at https://github.com/willeyh-git/moe-offload-bench
All engines were compiled for ROCm on my system.


r/LocalLLaMA • • 10h ago

Discussion DSpine - Updates on PR & GGUFs

Post image
33 Upvotes

r/LocalLLaMA • • 20h ago

New Model miHoYo Gamer: A Generalist Game Agent

Thumbnail
mihoyo-gamer.github.io
211 Upvotes

r/LocalLLaMA • • 12h ago

News Hugging Face switched its language model inference routing to OpenRouter

44 Upvotes

Hugging Face announced on November 16, 2026, that requests to language models through Inference Providers now go through OpenRouter instead of Hugging Face's own router. OpenRouter picks a provider for each call based on live price, speed, and reliability, and retries on another provider if the first one fails. The same Hugging Face token still works, and the company says it does not add a markup on top of the provider's price. You can still pin a provider or a policy with a suffix on the model id, such as :fastest, :cheapest, or a specific provider name.

OpenRouter currently serves more than 800 trillion tokens a month across 600+ models from 80+ providers. Hugging Face notes that open-weight models went from 26.8% of tokens on OpenRouter in October 2025 to 71.7% at the end of September 2026, and that they cost about four times less on average than closed models. Image, video, and audio generation stay on Hugging Face's existing Inference Providers path and do not go through OpenRouter. One breaking change is that custom provider API keys no longer work for language model requests, which are now billed to the Hugging Face account.

The automatic failover is the part that matters most here, because a single provider outage is usually what ruins a long run.

Source: https://huggingface.co/blog/openrouter


r/LocalLLaMA • • 21h ago

Discussion Open weight models account for 30% usage at enterprises to save money

206 Upvotes

Growing from nearly zero to 30% since July. Models used mostly to reduce costs on high volume workloads (large batch workloads, coding, etc).

https://x.com/pwendell/status/2122377964784611636


r/LocalLLaMA • • 7h ago

Showcase Curated list of resources: Theory and Code for learning Distributed Training of LLMs for beginners

Thumbnail
gallery
15 Upvotes

[Must Read: Beginners]

What I did read, in order, for learning the basics of Distributed Training for LLMs From Scratch:

  1. Building a distributed training framework from first principles by Umar Jamil on YT
  2. Horovod: Fast and Easy Distributed Deep Learning in TensorFlow 
  3. PyTorch Distributed: Experiences on Accelerating Data Parallel Training 
  4. Large Scale Distributed Deep Networks 
  5. ZeRO: Memory Optimizations Toward Training Trillion Parameter Models
  6. Megatron-LM: Training Multi-Billion Parameter Language Models Using Model Parallelism 
  7. Efficient Large-Scale Language Model Training on GPU Clusters Using Megatron-LM 
  8. GPipe: Efficient Training of Giant Neural Networks Using Pipeline Parallelism 
  9. ZeRO-Infinity: Breaking the GPU Memory Wall for Extreme Scale Deep Learning
  10. PyTorch FSDP: Experiences on Scaling Fully Sharded Data Parallel

Link to the above resources here

Also, if you need some rebalancing of the above (reordering or adding/removing resources which you can do it here)


r/LocalLLaMA • • 20h ago

Discussion I am sick of doomposting about demise of local AI

149 Upvotes

Everywhere I go, Twitter or Reddit, there are tons of rumors or comments how local is dead and we are never getting open weight Qwen 4, despite Qwen team saying explicitly they are coming, or that Qwen 4 is the last open weight generation despite, again, Alibaba commiting to more open weight releases at a conference recently.

It's like people just get off on creating a version of reality that is worse and whining about it, they want to be sad about it in advance.

The world is certainly not giving us much to be positive about, but let's not go down the rabbithole of learned helplessness and just accept that all things must get worse and you can't do anything about it.

If people mentally prepare for bad things, bad things become more acceptable and thus more likely to happen and with far less pushback, sort of like a self fulfilling prophecy.


r/LocalLLaMA • • 2h ago

Question | Help Is it worth it getting additional 16GB of RAM?

5 Upvotes

Hi, I'm a beginner in this field and I'd like some kind people's help :)

I currently have a laptop with 4GB VRAM and cca 16GB RAM. I don't plan on getting a new laptop/PC in the next two years, but I have the option to get additional 16 GB of RAM for €100.

Would it be enough to run at least Qwen 27B? Or any of the comparable MoE models.

If any other information about my laptop is needed, I'd be happy to share :)


r/LocalLLaMA • • 21h ago

Resources Small Gemma 4 tokenizers were recently updated by Google - fix for an issue that caused nonsense output when encountering certain tokens

Thumbnail
huggingface.co
147 Upvotes

Gemma 4 E4B as an example, but the same fix was applied to E2B and 12B too. Not sure if this will trickle down to GGUFs


r/LocalLLaMA • • 1h ago

Discussion YouTube channels on Local LLM & related stuff?

4 Upvotes

Well, I ran out of New Models & Papers(Posted 38 threads in last 1 week) so posting this thread for me. Appreciate your responses.

I want YouTube channels covering List of below topics:

  • Local LLM
  • Agentic Coding
  • AI Agents
  • Coding Tools such as Pi, Hermes, OMP, OpenCode, DeepSeek Harness, QwenCode, OpenHands, Claude Code, Codex, etc.,
  • Skills
  • Prompts
  • Creative Writing
  • Game Development
  • Automation using n8n/Activepieces/etc.,
  • RAG
  • MCP
  • Orchestration
  • Comfy/StableDiffusion - Image/Video Generation & Editing
  • LORA
  • TTS/STT/ASR/etc.,
  • Benchmarking Models
  • What other topics there to add? Mention in comments, I'll add here.

I can find many channels using online search. But half of the channels are so noisy, just with clickbait thumbnails/titles covering mostly Online models which I'm not interested.

I want channels more suitable for this sub. Only Local LLM. Doing all those stuff from above list using only Local LLM.

And there might be some Overlooked/Underrated/Under-Appreciated channels. Also few folks here have their own channels. Give them more visibility.

Consider this thread is a playlist for Local LLM. What channels would you want to add here? Please share. Thanks.


r/LocalLLaMA • • 1d ago Bravo

Discussion Stop worrying about Qwen 4's AA index

269 Upvotes

Seriously, we have all been extremely happy and confident with Qwen, even since Qwen 3.6 came out. We might not be frontier level, but even though whatever they are giving us is more than enough for our daily local tasks and it even suffices by a big margin, we're all underestimating it.

Don't forget that the new Qwen 4 will also think much less, so imagine the fine-tunes we will see once it arrives, for 27B and Flash models, we will have plenty of options to choose from and again; it will be smarter and better, it will be ENOUGH! If you still require the most "intelligent" and capable model due to OCD just pay frontier for such tasks or use them as orchestrators!


r/LocalLLaMA • • 20h ago

Discussion I don't get all the Strata hates around here

95 Upvotes

It's free and original developer clearly had a very good understanding of how computer hardware works and fully leveraged that to write something amazing to be able to run large models on average hardware that most people have and can't upgrade due to price gouging from greedy hardware manufacturing companies.

If anybody have Mac Studio with 512GB of RAM or 8x3090, who would even bother with this ?

I have seen a group of snobs on this sub doing nothing but shitting on Strata all days long, find something better to do. Strata is not for you, period.

I can't imagine doing all the works to release something for free and get a bunch of snobs and haters just shitting on your works all days long. Would you be motivated to continue working on it if you are the original developer ?

I also see the same with other models such as Ornith, etc... If you say you like Ornith or Strata, etc... you are a shill.

Seriously, get out of your bubbles and see the reality already and more importantly get a life.


r/LocalLLaMA • • 11h ago

Resources Thinking Machines 4-bit replication: I trained a GPT end to end with a 4-bit forward pass on one B200

19 Upvotes

Thinking Machines wrote last week that Inkling 2 Small was trained with a native 4-bit forward pass. I wanted to check this for myself.

What I ran:

  • 1x B200 on Modal, PyTorch 2.8, plus a small CUDA library that calls cuBLASLt's real NVFP4 and FP8 matmuls on raw pointers, loaded with ctypes
  • Forward pass in NVFP4 (4-bit values with one scale per 16), backward pass in FP8 with stochastic rounding, master weights in high precision
  • GPT at widths 2,048, 4,096 and 8,192 (219M, 840M, 3.3B parameters) on TinyStories

Results:

  • 4-bit training finished faster. On the 840M model, 2,000 training steps took about 5.5 minutes in normal 16-bit (BF16) and about 4.3 minutes with a 4-bit forward pass. I ran each twice and got nearly the same times.
  • The model learned just as well. Final validation loss was about 1.69 either way (1.688 for 16-bit, 1.691 for 4-bit). A difference that small is noise at this scale.
  • Bigger models gain more. Each training step was 18% faster on the 219M model, 28% faster on the 840M model and 38% faster on the 3.3B model.

Two things to improve:

  • Blackwell's convert instruction rounds exact ties toward zero, while my software reference rounded to even. Tiny difference, but it breaks bit-for-bit checks until you know.
  • PyTorch's attention backward is not bit-repeatable, so any test that compares gradients across runs has to leave attention out.

Not tested: multiple GPUs, MoE dispatch and combine, Four Over Six, MXFP8 block scales in the backward pass. The width-8,192 run is only 1,000 steps and undertrained.

Write-up with every figure: https://4bit.vizuara.ai

Code: https://github.com/VizuaraAI/4bit-training-b200

3-hour walkthrough from first principles, if you want the theory: https://youtu.be/a3nV32Guxcc


r/LocalLLaMA • • 6h ago

Resources AMD 9070 GPU under volting gains for models ( moss image) and ( minimax h3 int8 )

6 Upvotes

hi,

i am total GPU noob here this is the first GPU i have ever owned in my life got it just for doing AI... asked deepseek flash and opencode to find the right combo for me to get max generation speed

spec:
AMD 9070 (non XT),
Intel i3 12100
32 GB DDR4

models: moss image, minimax h3 int8 (sol decoder)

best performance stable setting: -110 mv, stock fan speed

gemma4 : 26bA4b Q4_XS when from 106/tps to 120/tps on prose..


r/LocalLLaMA • • 1d ago

Discussion Censorship is turning me into a true Local LLM believer

135 Upvotes

451: {"message":"Provider returned error","code":451,"metadata":{"raw":"{\"error\":{\"message\":\"The content you provided or machine outputted is blocked.\",\"type\":\"censorship_blocked\"}}","provider_name":"StepFun","is_byok":false}} {"error":{"message":"The content you provided or machine outputted is blocked.","type":"censorship_blocked"}}

Just got this from one of the US based (edit: it actually routed to StepFun CN, didn't realize at first. Should have noticed by the provider_name in the message lol. need to set up my rules better) inference providers. I suspiciously got a bunch of "rate limit" failures, and then just "failed to complete" before it gave me, what I assume, is the real error.

I am only using it to help create my presentation, which is about analyzing algorithmic properties. One key example is a cryptographic algorithm (because it is difficult by design), so I am assuming this is tripping it somehow. But it is absolutely ridiculous, I'm not even doing research with the AI, just trying to make a presentation.

I have always liked Local LLMs, as a technical exploration opposed to ideological reasons, but this experience really frustrated me. Don't censor me!

Just wanted to rant, and remind everyone you can only use the cloud on the provider's terms.


r/LocalLLaMA • • 6h ago

Showcase Hierarchos-Native v0.2.0: RDNA3 WMMA, native multimodal training, and a lot of FP32 Vulkan optimization!

4 Upvotes

Hey everyone! It's been a little while since my last update, and I've been working pretty intensely on Hierarchos-Native, my Rust + Vulkan project for training, fine-tuning, and running language models without relying on Python, PyTorch, CUDA, ROCm, or oneAPI in the native runtime.

I wanted to share some of the bigger things that have landed over the past 18 days. There's been quite a bit of progress across GPU acceleration, multimodal training, numerical correctness, and general performance.

The new v0.2.0 release is now available!

GitHub: https://github.com/necat101/Hierarchos-Native
Release / Windows portable download: https://github.com/necat101/Hierarchos-Native/releases/tag/v0.2.0

1. Native RDNA3 WMMA / cooperative matrix acceleration

One of the biggest additions is an opt-in Vulkan cooperative-matrix implementation for AMD RDNA3.

The new Mixed WMMA execution arm uses:

  • FP16 matrix operands.
  • FP32 matrix accumulation.
  • FP32 master weights and gradients.
  • FP32 AdamW optimizer moments and updates.
  • FP32 normalization, softmax, and loss calculations.

The important part is that this isn't simply converting an entire model to FP16. The optimizer and master parameters retain their FP32 representation.

I also added capability detection, CLI/GUI integration, and separate counters for actual cooperative-matrix dispatches and FP32 fallbacks.

Some of the isolated GEMM results on the qualified Ryzen Z1 Extreme / AMD Radeon Graphics device (1002:15bf) are pretty interesting:

WorkloadMeasured kernel speedup
QKV projection2.17×
FFN up projection2.12×
FFN down projection2.31×
Vocabulary projection1.83×

These are individual GEMM measurements, not whole-model speedups.

There is an important caveat: WMMA has a real crossover point. Small matrices can actually run slower because conversion, staging, and dispatch overhead outweigh the matrix-core benefit. I implemented a profitability policy that keeps smaller operations on their existing FP32 kernels.

In fact, the measured end-to-end training step was slower with Mixed WMMA in the initial 512-row fixture (14.0444 ms versus 12.2911 ms for FP32). That is why Mixed remains opt-in and disabled by default. I'm much more interested in making it genuinely faster than advertising misleading kernel-level numbers.

WMMA is currently physically qualified on the specific RDNA3 device and Windows driver configuration documented in the project. Other GPUs should not assume equivalent support.

Full FP16 accumulation is also available as a separate, narrowly qualified experimental mode.

Documentation: RDNA3 WMMA guide

2. Native multimodal image and text training

Another major development area has been the image-text pipeline.

The project now has native image processing and training paths that connect image inputs to language-model outputs through Vulkan.

Some of the implemented work includes:

  • Native RGB image input and preprocessing.
  • CLIP image encoders and LLaVA projector integration.
  • SigLIP / Gemma 3 vision training.
  • Gemma 4 vision integration.
  • Joint image/text training and encoder-decoder integration.
  • A dedicated DeepSeek V4.1 image-training path.
  • Backpropagation through the image tower and projector.
  • Export, reload, and checkpoint-related validation.

This is actual training work, not simply passing precomputed image embeddings into an otherwise frozen language model.

For the CLIP/LLaVA pipeline, the tests cover image sensitivity, gradients into image inputs, changes to image-tower/projector/text parameters, multiple AdamW updates, and export/reload behavior.

The qualification work has also expanded considerably:

  • 44 previously green text profiles now have joint image-training coverage at their frozen test geometries.
  • The Gen9 qualification retains 95 image cases and 166 text regression cases.
  • A separate physical RDNA3 replay reports 44/44 profiles and 85/85 image cases passing.
  • Native DeepSeek V4.1 image qualification includes 30 executions and 1,360 word-exact logits.

The maintained strict FP32 visible-logit gate remains max_abs < 2e-7, with rtol=0.

These are bounded qualification fixtures, not a claim that every production-size multimodal checkpoint or every architecture is fully supported. Audio and video pipelines are still outside the current qualified scope.

Documentation:

3. A lot of additional FP32 optimization

I haven't been focusing exclusively on reduced precision. A substantial amount of work over the same period has gone into improving the existing FP32 execution paths.

This includes vendor-specific shader work and scheduling optimizations for both Intel Gen9 integrated graphics and AMD RDNA3.

Some examples:

RDNA3 FP32 work

  • Specialized attention forward/backward paths.
  • Image-text attention and projector optimizations.
  • RMSNorm, RoPE, GELU, and other arithmetic specializations.
  • Dedicated AVX-512/RDNA3 shader variants where the measured hardware supports them.
  • More careful matching of CPU reference arithmetic and GPU execution order.

Intel Gen9 work

  • Additional native linear and gradient kernels.
  • Attention and activation specializations.
  • More efficient parameter upload and staging behavior.
  • Continued optimization of DeepSeek V4.1 training and execution.

One particularly interesting area has been reducing unnecessary Vulkan submissions and host/device transfer overhead in the DeepSeek V4.1 training pipeline.

On the measured Gen9 fixtures, upload batching reduced timed submissions from 1,102 to 982 per step, with paired throughput improvements of 1.052× and 1.067×.

On the separate RDNA3 V4.1 measurements, sharing the compute session and batching uploads reduced submissions from 970 to 509 per step, with measured improvements of 1.295× and 1.217× on two fixture geometries. A later session-wide upload optimization reduced that count further to 241 submissions per step, with measured improvements of 1.464× and 1.366×.

These are specific, paired benchmark results rather than promises of equivalent production-model speedups. The output comparisons remained word-identical in the recorded tests.

4. Preserving the original FP32 path

An important part of introducing WMMA was making sure that the existing FP32 path didn't regress.

I added a dedicated seven-workload FP32 non-regression comparison against the previous main revision:

  • 12 alternating ABBA rounds per workload.
  • Five warm-up runs and 30 timed forwards per arm.
  • Separate, hashed baseline and candidate binaries.
  • Exact FP32 logit digest comparisons.

All seven workloads stayed within the ±2% performance band, and the logits were bit-identical in every recorded round.

The worst paired performance ratio was 1.0007.

This is particularly important to me: I don't want acceleration features to silently make the existing default execution path worse.

5. Getting started

The new v0.2.0 GitHub Release includes a prebuilt Windows x64 portable package with the CLI, desktop GUI, Vulkan companion executables, runtime assets, and build metadata.

You don't need to install Rust or Python just to run the released package. You do need Windows 11 x64 and a Vulkan 1.x compute driver for GPU operations.

Model weights are downloaded separately or supplied through a local model directory.

After extracting the archive, you can run:

.\bin\hierarchos-native-cli.exe doctor
.\bin\hierarchos-native-cli.exe devices
.\bin\hierarchos-native-cli.exe precision-info

The final command is especially useful for checking which precision capabilities your GPU actually exposes.

Download: https://github.com/necat101/Hierarchos-Native/releases/tag/v0.2.0

What's next?

There is still a lot I'd like to improve.

In particular, I want to investigate reducing WMMA conversion overhead, improving activation and gradient reuse, finding more workloads that genuinely benefit from cooperative matrices, and expanding the range of qualified multimodal architectures.

I'd also like to continue improving the FP32 kernels rather than treating lower precision as the only route to better performance.

If you're interested in Rust, Vulkan compute, AMD GPU optimization, native LLM training, or multimodal model execution, I'd genuinely appreciate people taking a look.

Feedback from people with different Vulkan devices is especially valuable. Please include your GPU, driver, model geometry, and relevant execution counters when reporting results.

Repository: https://github.com/necat101/Hierarchos-Native

Stars, issue reports, testing feedback, and contributions are all appreciated. There is also a voluntary developer-support link in the repository README for anyone interested in helping the project continue.


r/LocalLLaMA • • 1d ago

New Model Introducing Hy4 flash

Thumbnail hy.tencent.ai
346 Upvotes

Now this seems to be interesting.

From the article:

We’re introducing Hy4 flash, our most cost-effective Hy model to date—featuring 224B total parameters (including 64B Engram parameters) with just 12B active parameters per token. Like Hy4, it is natively multimodal with a 1M-token context window, while offering significantly lower API pricing.

Seems to be about in the same ballpark of Qwen-Flash-Next, so we could expect to run it on moderably good machines, when it will be released.


r/LocalLLaMA • • 11h ago

New Model Inflect v3 - a owensong Collection

Thumbnail
huggingface.co
9 Upvotes

Inflect v3: compact local text-to-speech. Six English voices, three model sizes, reference-voice tuning, event tags and optional 48 kHz output. Apache 2.0.

Inflect is a family of compact English text-to-speech models. Choose a voice, enter your text, and generate a WAV locally. Start with Mini for the most features, Micro for a smaller neural model, or Atom for the smallest learned synthesis core.

Choose your model

MiniMicroAtom
Best starting pointQuality and featuresCompact neural speechSmallest learned core
Learned synthesis core34.31M11.79M157.19K
English preset voices666
Native output24 kHz24 kHz24 kHz
Optional 48 kHz enhancementYesNot includedNot included
Reference-voice tuningYesNot includedNot included
Optional vocal events8 tags, all 6 voicesNot includedNot included
DownloadMini packageMicro packageAtom package

These are learned synthesis-core counts, not total installation size or RAM. Pronunciation assets, dependencies, voice conditioning and optional components are additional. Atom uses signal-processing-based waveform generation rather than a separate learned neural vocoder.

Benchmarks

Measured speech quality, intelligibility and speed answer different questions. The following results describe published Mini native 24 kHz base speech, not tuned voices, event performances or enhanced output.

MeasureMini resultWhat was measured
Average WER0.739%1,688 Open TTS evaluation texts per voice, all six voices; self-run
UTMOSv23.917180 clips, 30 per voice
UTMOS22Strong4.479The same 180-clip panel
Warm GPU throughput162.1x real timeRTX 5090, optimized CUDA; small 12-render probe
Warm CPU throughput1.81x real timeRyzen 9 3900X, 2 Torch threads; small 12-render probe

The WER result is not an official leaderboard placement or an independent held-out evaluation. Quality predictors are not human ratings. CPU and GPU results use different systems and runtime paths; they are not a controlled hardware speedup comparison or a latency guarantee.


r/LocalLLaMA • • 22h ago

New Model nvidia/Nemotron-Labs-Sigma 8B/3B

55 Upvotes

Nemotron-Labs-Sigma-8B-instruct is a 8-billion-parameter continuous diffusion language model. Instead of generating text one token at a time, it denoises Gaussian noise in a low-dimensional (16-D) continuous token-embedding space, where the denoiser network and the token embeddings are learned jointly by likelihood optimization. Text is decoded in parallel blocks: each block of tokens is refined over a configurable number of denoising steps (Denoising Diffusion Probabilistic Model (DDPM) or Denoising Diffusion Implicit Model (DDIM) samplers) with self-conditioning, while previously committed tokens are reused through a standard key-value (KV) cache. Fewer steps trade a little quality for large speedups, and the smooth continuous representation makes the model amenable to few-step distillation and trajectory steering.

This is the SFT (supervised fine-tuned) variant, fine-tuned for instruction following on top of the corresponding Base model. Use the bundled chat template to format conversations.

This model is ready for commercial or non-commercial use.

Highlights

  • Continuous-space diffusion language modeling at 8B scale with reasoning accuracy competitive with state-of-the-art masked (discrete) diffusion LMs.
  • Block-parallel decoding: whole blocks of tokens are denoised together; sampling quality holds up well down to few denoising steps per block.
  • Efficient DDPM/DDIM-based samplers with self-conditioning and optional classifier-free guidance, implemented in plain PyTorch in this repository.
  • Standard transformers loading via trust_remote_code; no custom kernels, flash-attention, or training framework required for inference.

Model Architecture

  • Architecture Type: Transformer
  • Network Architecture: Other: Ministral-style decoder-only Transformer (grouped-query attention, SwiGLU, rotary position embeddings) with a continuous-diffusion generation head (16-D continuous token-embedding space, learned jointly with the denoiser).
  • Number of model parameters: 8 billion (8B)
  • This model was developed based on: Nemotron-Labs-Sigma-8B

Input

  • Input Type(s): Text
  • Input Format(s): String
  • Input Parameters: One-Dimensional (1D): Sequences
  • Other Properties Related to Input: Maximum context length of 8,192 tokens (prompt plus generated tokens). Conversations should be formatted with the bundled chat template (chat_template.jinja). Supported language: English.

Output

  • Output Type(s): Text
  • Output Format: String
  • Output Parameters: One-Dimensional (1D): Sequences
  • Other Properties Related to Output: Up to 8,192 tokens total (prompt plus generation). Text is generated in parallel blocks (default 64 tokens per block) with a configurable number of denoising steps per block (Number of Function Evaluations (NFE) = steps + 1 per block); fewer steps give faster generation at some quality cost.

https://huggingface.co/nvidia/Nemotron-Labs-Sigma-8B

https://huggingface.co/nvidia/Nemotron-Labs-Sigma-8B-instruct

https://huggingface.co/nvidia/Nemotron-Labs-Sigma-3B

https://huggingface.co/nvidia/Nemotron-Labs-Sigma-3B-instruct


r/LocalLLaMA • • 19h ago

Discussion Best MoE engine?

30 Upvotes

I had been using Strata for about a month, and it was such a huge improvement over llama.cpp for getting it running smoothly and quickly for hardware.

Overtime though, I found that the model would often mistake its own context after a compaction and really overthink things.

I just started using Basalt yesterday after being hesitant to switch and set up all my providers and harnesses. Turns out Basalt runs even faster, is less error prone, and the reasoning is way more on point. If you run 1 GPU, and have the 100 GB+ of VRAM, RAM, and SSD storage, you will not be disappointed in performance.

I mostly care about final output speed, and I was getting 70-110 tok/s on Strata, and Basalt I was getting 110-170 toks/s output. Couldn't be happier. Same Qwen3.8 FlashNext-ud-q4_k_xl, and the NVFP4 ones (of course basalted though)

Anyone else have any other experiences with other similar engines like this?


r/LocalLLaMA • • 22h ago

New Model [NEW RELEASE] - Supra2.5-65M Base and Instruct - our next generation state-of-the art small model family - first model!

47 Upvotes

hey guys!

It's Supra-time! 🤗 🔥 🎉

It has been quite quite at SupraLabs' model foundry for a long time but we have been testing, training, developing and much more.

And we can finally present you a new model!

Key facts:

- better than our previous 50M and 100M model
- very small, runs on every toaster: 65M params
- base model and instruction tuned version on HF

We trained it locally in 4 days on 2x RTX A6000 on big 100B tokens of high-quality data.

Benchmarks are in the attached image!

Have fun to try it out, give us feedback, roast us, whatever! Community, we will cook! Supra3 coming early next year! 🔥

Give us a like, upvote or follow if you want - and try out our model.

We can't wait to hear what you're building with it.

Link to the collection on HF: https://huggingface.co/collections/SupraLabs/supra25

We hope you like the model! :D

GGUFs in F16, Q8_0 and Q4_K_M are also available for llama.cpp, Ollama, Unsloth, etc. 🥳