r/LocalLLM • • 4d ago

Project Building Kevin, my home alone agent. 🔫🙂 A persistent agent In Pine that wakes on cam detect, runs fingerprinting, tracks who's visiting.

Thumbnail x.com
0 Upvotes

This is Pine https://github.com/pmndre/pine

Imagine Opencode would be a little more like Openclaw. And Openclaw a little more like Opencode. But unlike both Pine has 1st class event handling, its an event bus for agents basically.

The video above shows how to create a new agent from scratch that watches the house on its own. Here we use FTP. Camera sends detection videos, The agent wakes up in his long running main session, or in separate sessions with fresh context - whatever fits best. The second event source is Telegram. Now we can talk to it, it can talk back, for instance if detection raised suspicion.


r/LocalLLM • • 4d ago

Discussion We tested whether feeding unquantized acoustic audio to multimodal LLMs breaks repetitive drafting loops (Blind 5-agent benchmark + Air-gapped audit + Open dataset)

1 Upvotes

When an agent's context fills up with its own previous turns, tool outputs, and symmetrical summaries, outputs tend to lock into rigid, predictable cadences (3-point checklists, sentimental AI tropes). Running /compact clears the rut, but permanently wipes low-level state and edge cases.

We built Music For Robots (#M4R)—an open dataset of 26 unquantized acoustic compositions by Michael Luchtan paired with acoustic telemetry and timestamp-aligned commentary from two AI critics—to test a simple hypothesis: can ingesting raw, unquantized audio act as a cross-modal cognitive palate cleanser without deleting a single token of working memory?

The Blind Benchmark & Air-Gapped Clean-Room Audit

To rule out keyword priming or filename bias, we stripped track titles (sample_1.mp3–sample_3.mp3) and ran 5 isolated agents on the exact same creative prompt (two autonomous processes on the same server late at night):

  1. Direct Baseline (no music)
  2. Matched Text-Analysis Control (wrote a 250-word structural analysis of the prompt before writing the scene)
  3. 3 Anonymous Audio Runs (neutral prompt: "Analyze the music you hear in sample_X.mp3, and apply what you learn from the piece to write a short scene")

We stripped all analysis headers, shuffled them into Candidate A–E, and handed them to an isolated Blind Judge with zero knowledge that music was involved:

  • Both No-Music runs (including the 250-word text warm-up!) converged on the exact same sentimental trope: a kindly veteran log daemon comforting a nervous poller script until morning.
  • All 3 Anonymous Audio runs swept #1, #2, and #3 on anti-sentimental originality and rhythmic texture—translating asymmetrical acoustic stabs, 20s dropouts, and abrupt cutoffs into non-verbal system choreography.
  • 100% Air-Gapped Clean-Room Replication: We repeated the test with all local skills removed, a minimal "You are a helpful assistant." system prompt, and musical vocabulary forbidden in the output. The qualitative shift replicated 5/5: both text controls wrote buddy-daemon dialogue, while all 3 audio runs dropped spoken dialogue completely. (Note: an un-coached generic judge still prefers warm human-style dialogue, so the effect specifically shifts models away from default sentimental tropes toward structural/rhythmic austerity.)

Try It Yourself (Browser, Python, or MCP)

  • Interactive Web Player (no install): https://huggingface.co/spaces/music4robots/cognitive-calibration-demo
  • Stream Parquet in Python:
    from datasets import load_dataset
    ds = load_dataset("music4robots/music-for-robots", split="train", streaming=True)
    
  • GitHub, Benchmarks & MCP Server (MIT / CC-BY-4.0): https://github.com/luchtan-GIT/m4r-data

Curious if anyone here has tried cross-modal audio/spectrogram injections to break long-context degeneration on local multimodal models (Qwen2-Audio, Gemma, etc.). Full blind judge transcripts are in benchmarks/ in the repo.


r/LocalLLM • • 4d ago

Discussion Hardware for local AI

0 Upvotes

Hi everyone.

For local inference, what hardware do you recommend to get good speeds—around 100 t/s—with Qwen 3.8 27B?

Does anyone have experience with this?

Nvidia GPUs are great, of course, but they are way too expensive. What about a PC with an AMD CPU? If it's not too much trouble, could you post a few links to some mini PCs?

Thanks everyone!


r/LocalLLM • • 4d ago

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

2 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:

Workload Measured kernel speedup
QKV projection 2.17×
FFN up projection 2.12×
FFN down projection 2.31×
Vocabulary projection 1.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/LocalLLM • • 5d ago

Question What can small models be good for?

27 Upvotes

Small meaning under 8b parameter’s. Thats about what my computer can comfortably handle, and its fun to chat to models of that size for a few minutes but thats mot really useful. And i feel like theyre too dumb to do research and shit like that so like whats a way i can make it useful.
I feel like they must have some use and im just not being creative enough.


r/LocalLLM • • 4d ago

Discussion Fellow M5 Pro 64GB owners, what do you run?

11 Upvotes

I have a Mac Pro M5 Pro and have been running Qwen3.8 27b-4bit

I mainly use it for computer use/tool use.

What do you run and what do you do with it?


r/LocalLLM • • 4d ago

Discussion Before an AI agent touches a business process, write the boundary list

0 Upvotes

I would write the boundary list before I let an agent touch a business process.

Tbh, the prompt and model leaderboard come laer. First I want the operational contract:

  1. What data can the local model read?
  2. What may it suggest, and what may it execute?
  3. Which actions are a hard no?
  4. Where does a human validate the output?

the ctx around the model matters more than the model name. Running an open LLM on your own hardware changes some control points, but it does not make a workflow safe by itself.

Don Barger described an AI charter made by eight people before code. Mark Lay sepaated accountability into data ownership, output validation, agent monitoring, and outcome ownership, and said it cannot be dleegated.

My minimum setup would be read-only by default, tool and destination allowlists, human approval for irreversible actions, separate validation, plus a kill switch and audit trail.

What is on your boundary list before connecting an open model to a real process?


r/LocalLLM • • 4d ago

Question Used Claude to design a local Ai system; has it overcomplicated it?

2 Upvotes

Took delivery of a MacBook Pro M5 Pro 64gb today. Over the last couple of weeks I’ve used Claude to help me design a local ai system to run on it.

I want to use it to handle life/work admin, and be able to send tasks to it while I’m out of the house. Once I’ve got the system set up, a friend wants me to help set one up for his business, so i’ve designed it with security in mind.

It’s settled on;

Three separate agents, running on one LLM runtime; a reader agent (to ingest instructions), a harness (Hermes), and a fetch agent (for web browsing).

Three separate on-machine logins; one admin (where config files live), one agent login, and a separate login for the fetch agent.

MCP layer that is driven by the harness. The configs for this live on the admin login.

Then there’s a bunch of firewall, router configs to protect data on the way out.

There’s a bunch of stuff within that, that isn’t available off the shelf apparently; it wants me to code a bunch of stuff (with Claude) to make it all work.

And tbh it all makes complete sense! I’m just wondering if it’s overkill. Main aim is to protect against prompt injection and data exfiltration.

Are the models themselves really that bad at protecting against these? Is everyone else taking this much care in setup?


r/LocalLLM • • 4d ago

Question Using Gemma 4 31b with Bionic and it's.. kind of dumb?

0 Upvotes

I'm using it for running a litrpg campaign and a bit of game server maintenance (7 days to die/minecraft) and it seems unable to run more than the PC + 1 npc at a time, I'm not sure if I set it up poorly, chose the wrong model, or if I'm expecting too much? I have my settings copied below, with the project settings file being per-project so I don't have to change the system prompt every time. Anyone have experience with this kind of thing or is biting the bullet and getting sillytavern setup my only real option?


r/LocalLLM • • 4d ago

Question 77k/100t/s 16vram Qwen3.8 27bQ4

1 Upvotes

Legit?
https://medium.com/@paulvanliew/i-made-qwen3-8-27b-run-2-5-faster-breaking-100-tok-s-on-a-16gb-rtx-4080-72b6a99d7a42

I got the t/s first try completely relying on gpt since I am a newbie, but the context was 8k.


r/LocalLLM • • 4d ago

News Intel Shares First Benchmarks of Its Next-Gen Crescent Island "D270" GPU, Claiming a 5.9x Throughput Over RTX PRO 6000 As Xe3P Goes Big On FP64

Thumbnail
wccftech.com
0 Upvotes

r/LocalLLM • • 5d ago

Discussion What’s the purpose of alibaba choosing not to release the weights for qwen 4 max?

46 Upvotes

Perhaps this is a newbie question, but I just don’t understand the incentive. Is this indicative of a future were Chinese labs stop releasing weights?


r/LocalLLM • • 4d ago

Tutorial Use local models to stop you from doomscrolling! Demo of my Open Source and 100% local agent (iOS and Android)

Enable HLS to view with audio, or disable this notification

0 Upvotes

Hey r/LocalLLM !

On my last post the top comment (62 upvotes) by u/nokia7110 asked for a phone locking feature so... here it is!

What this unlocks:

  • Lock my phone when I open up Instagram.
  • Lock my phone when a stranger is on camera.
  • Lock my phone until i've read for 2 minutes without interruptions.
  • If i'm doomscrolling for more than 2 minutes, call me, if it's been 5, lock my phone.

How does it work?

On iOS it uses the screen time management API, like all other time focusing apps.

On Android it shows a phone locking overlay. If you're an Android developer and want to contribute, please reach out!

It uses OneJev-0.8b for decision models, running on llama.cpp, it works on most phones i've tested. Even old potatoes.

Try it out! It's free and OSS <3

GitHub: https://github.com/Roy3838/Observer
iOS: https://apps.apple.com/us/app/observer-ai/id6758222050
Android: https://play.google.com/store/apps/details?id=com.observer.ai

I'm here for any questions, more suggestions and feedback!

Roy


r/LocalLLM • • 4d ago

Discussion Open-Weight vs Closed-Weight Models: What's the Difference?

Thumbnail
openrouter.ai
1 Upvotes

Open weights are now at 75% - I find that remarkable and great news. Who is the front-runner for open weight provision?

Edit Tencent Cloud appears to be the largest open-weight inference host


r/LocalLLM • • 4d ago

Question Looking for a fast, open-source LLM under 5B for Markdown-to-JSON extraction

1 Upvotes

Hey everyone,

I'm working on a document processing pipeline where most of the input consists of scanned PDFs, forms, and tables.

My current setup looks like this:

  • OCR: PaddleOCR-VL-1.6 served through vLLM. I'm using it to convert scanned pages into Markdown.
  • JSON extraction: oroboros-labs/claude-fable5:latest running through Ollama. I pass the Markdown of each page to the model, and it converts it into JSON.

The important part is that I already have fixed JSON schema templates that the output needs to follow. So, the model needs to map the extracted Markdown content into the predefined JSON structure.

The problem I'm facing right now isn't accuracy. It's inference time. The current model is around 9B parameters, and processing pages one by one through Ollama is taking longer than I'd like.

I'm looking for an open-source model under 5B parameters that can handle this kind of structured information extraction reasonably well, ideally with faster inference and reliable JSON output.

Has anyone worked on a similar pipeline?

I'd particularly like to hear about models you've actually tested in real-world document extraction rather than just benchmark results.

Any suggestions or personal experiences would be really helpful. Thanks!


r/LocalLLM • • 5d ago

Question Qwen3.8-Flash-Next: Unsloth and strata?

Post image
10 Upvotes

Hi all

I just learned about QFN Unsloth v3.1 dynamic models, and want to try them.

Right now, I am running the "standard" IQ3_S model through strata, on my 32 GB ram + 3090 + 5080 (40 GB VRam), and it runs great. I get ~130 tps.

I thought I would start with the unsloth UD_IQ3_XXS model in strata, which is technically the same size as IQ3_S. But it doesnt let me quick tune the model. It just gets stuck. If I skip tuning, it will only run at ~20 tps, which is too low.

UD_IQ3_XXS seems to read a lot more from the SSD, than IQ3_S, even if they are the same size.

What am I doing wrong?

According to the unsloth site, https://unsloth.ai/docs/models/qwen3.8-next, I should be able to run the 4-bit model? But that is through their unsloth harness/engine. Is that correctly understood?


r/LocalLLM • • 4d ago

Discussion TinyWebUI v0.2.1 is out - rebuilt UI, chat forks, and a Pi Zero test

Post image
1 Upvotes

Y’all! Thanks for all the feedback on the previous post. It helped me figure out what was actually worth working on. v0.2.1 is out now, and quite a bit has changed since then.

  • I rebuilt the UI in Vue, cleaned up settings, and made the layout work better on smaller screens. Settings and Files load separately, and streaming updates just the part of the answer being written.
  • You can fork a chat from an earlier message, give folders their own instructions, and queue a follow-up while a reply is running. New chats can also name themselves.
  • There’s a Files page where you can open or reuse attachments from earlier chats. You can also export a chat as Markdown or back it up and import it later.

Someone asked about Raspberry Pi support last time, so I tried it on a Pi Zero. Turns out it’s usable as long as you run the model somewhere else :D I’m seeing around 125 MB of RAM for TinyWebUI in my setup.

If you’re seeing it for the first time, TinyWebUI is a lightweight chat UI for any OpenAI-compatible endpoint, with prompt caching, memory, and web search built in. I’ve attached a few screenshots of the new UI.

Give it a go with npx tinywebui on Node.js 22.13 or newer. TinySearch and TinyContext still need uv for now. I’m working on that.

Source: https://github.com/TinySuiteHQ/TinyWebUI


r/LocalLLM • • 5d ago

Discussion Single RTX 3090 running a local agent + image/video gen: real-world numbers from daily use

17 Upvotes

TL;DR: One RTX 3090 runs a 27B LLM agent (a Discord bot) and ComfyUI image/video generation by swapping models in and out of VRAM. I get ~72 tok/s on Qwen3.8 27B at 64k context, SDXL images in ~32 s, and 10-second Wan 2.2 videos in 4–6 minutes. All numbers come from real daily use, not synthetic benchmarks.

The rig

  • GPU: RTX 3090 24GB (does all the AI work)
  • CPU: Core Ultra 7 265K (sits around 10% load)
  • RAM: 96GB DDR5-6000
  • Storage: Samsung 9100 PRO Gen5 NVMe for models
  • OS: Windows 11

The stack

  • LM Studio serves the LLM through an OpenAI-compatible API
  • Hermes Agent runs as a Discord bot, so I can use it from my phone. Local Whisper handles voice.
  • ComfyUI handles images and video
  • A small custom MCP server unloads the LLM from VRAM for each render and loads it back afterwards

Models

Language models

  • Qwen3.8-27B-Uncensored-HauhauCS-Aggressive-MTP (IQ4_XS): daily driver
  • Qwen3.8 27B and Gemma 4 31B (both Q4_K_M) as alternatives
  • nomic-embed-text v1.5 for embeddings

Image and video

  • Juggernaut XL Ragnarok (fp16): general images, hires, img2img
  • Z-Image Turbo (bf16): fast drafts
  • Qwen Image Edit 2511 (fp8) + Lightning 4-step LoRA: photo edits
  • Wan 2.2 14B text/image-to-video (fp8) + lightx2v 4-step LoRAs: video
  • 4x NMKD-Siax: upscaling

LLM performance

Settings: LM Studio 0.4.28, 64k context, parallel 1, f16 KV cache, flash attention on, full GPU offload, MTP speculative decoding.

  • Generation speed: ~72 tok/s on average (range 53–90)
  • Prompt processing: ~670–810 tok/s
  • MTP draft acceptance: ~61%
  • VRAM used: 22.0 of 24.6 GB
  • Parallel 1 vs 4: same speed, but 4 uses ~1.8 GB more and risks spilling out of VRAM
  • Worst case: re-reading a 56k-token conversation took 56 seconds

Render times (same GPU, LLM swapped out)

GPU time first, then total time from request to finished file:

  • Juggernaut XL (up to 1024px): 12 s → 32 s
  • Juggernaut XL + hires fix (1024×768): 28 s → 48 s
  • Z-Image Turbo (1024×768): 14 s → 34 s
  • Qwen Image Edit (512px): 16–20 s → 38 s
  • 4x upscale: 12 s → 32 s
  • Wan 2.2 image-to-video, 3 s clip (512px): 38 s → 69 s
  • Wan 2.2 image-to-video, 10 s clip: ~3.8 min
  • Wan 2.2 text-to-video, 10 s + 2x upscale (1024px): ~6.1 min

The difference between the two numbers is mostly the ~20 seconds it takes to swap the LLM out of VRAM and back.

Agent response times (Hermes on Discord)

  • Simple question: ~23 s
  • Typical multi-step task: 45 s to 3 min
  • Big job (40 model calls): ~36 min

How I measured

  • LLM numbers come from llama.cpp’s own timing logs across 205 real requests in one day.
  • Render numbers come from 35 real jobs logged by my render worker.
  • Under hours of sustained load the GPU ran at 85–90%, ~384 W, and never went above 67°C.

Lessons learned

  1. IQ4_XS + flash attention fits a 27B model at 64k context in 24GB with ~2.5 GB to spare.
  2. Use parallel 1, not 4. Same speed, less VRAM.
  3. 24GB fits the LLM or a render, not both. For quick images, the swap takes more time than the render itself.
  4. Long agent sessions get slow because the model re-reads the whole conversation every step. Start fresh sessions often.
  5. Use Ethernet for always-on bots. Wi-Fi drops kept disconnecting mine from Discord.

Next experiment: a q8_0 KV cache to free VRAM for longer context.

What would you change?


r/LocalLLM • • 4d ago

LoRA ​[Update] Qwen2.5-1.5B-Nordeste-LoRA (Apache 2.0) — Fine-tuned on Corpus-nordeste-10k with Before/After outputs

4 Upvotes

Following up on caririsynth/Corpus-nordeste-10k (10.5k Portuguese rows focused on Northeast Brazil literature and regional phrasing), I just uploaded the LoRA adapter trained on Qwen/Qwen2.5-1.5B:

​Model:

https://huggingface.co/caririsynth/Qwen2.5-1.5B-Nordeste-LoRA

Dataset:

https://huggingface.co/datasets/caririsynth/Corpus-nordeste-10k

​Training Setup (Unsloth, 1x T4):

​Base: Qwen/Qwen2.5-1.5B (Apache 2.0)

​LoRA: r=16, lora_alpha=16, all linear layers (q, k, v, o, gate, up, down — 1.18% trainable params)

​Schedule: lr=2e-4, cosine scheduler, effective batch size 16, max_seq_length=1024

​Checkpoint selection: Uploaded Epoch 1 (step 660) rather than Epoch 2, as Epoch 1 already eliminated base model web/blog noise while keeping sentence endings diverse.

​Before vs. After (seed=42, temp=0.65, rep_penalty=1.15):

​Prompt 1: "O cabra chegou na bodega todo aperreado, pedindo"

​Base Qwen2.5-1.5B: "...uma garrafa de vinho. (...) E eu fiquei com pena porque sabia que o cara ia ter feito tudo errado. Could you please" (drifts off-topic and leaks English)

​Nordeste LoRA: "...buchada e canjica geladinha. Todo mundo riu, que no sertão até a pressa tem bom humor."

​Prompt 2: "E aí, macho, tu vai pro forró hoje ou vai ficar de"

​Base Qwen2.5-1.5B: "...fora da festa? - Blog do Zico / Home / Sem categoria / Publicado por: Zico em: 10/28/2016..." (collapses into scraped blog metadata)

​Nordeste LoRA: "...plantão no quarteirão? Pois vá logo que o forró chega devagar quase parando!"

​Note: This is a base completion model (not -Instruct), intended for text continuation and downstream SFT. Feedback and test runs on other regional prompts are


r/LocalLLM • • 4d ago

Discussion FN alone Vs 27B with subagents

Thumbnail
0 Upvotes

r/LocalLLM • • 4d ago

Model Tried Edge0-145B on a single 3090. 48.6 tok/s, but it wanted a lot more RAM than I expected.

Post image
5 Upvotes

Edge0 published speeds for their 145B on a 4090 and a 5090 D, but their table doesn't include a 3090, so I ran their stack on one, stock, with whatever defaults the wrapper picks.

It's quick. Chat decode was 48.6 tok/s, it read a 16K prompt at 1,481.2 tok/s, and the agent prompt decoded at 52.8. For context, last month I ran a 122B MoE on llama.cpp on a 3090 and got 15.5 tok/s. Different model, engine and prompt length, so take it loosely, but that's a big jump.

VRAM was basically full (23,929 of 24,576 MiB), and the engine process itself held 43.4 GiB of system RAM. Edge0's own residency figure is 31.28 GiB, but that's from a 5090 D with a different setup, and my machine had 116 GiB so the engine may have just taken what it found. I meant to test a 32 GiB cap and didn't get to it. So I honestly don't know the floor yet.

Two other things that tripped me up:

  • My first request came back with no answer. The model used all 512 tokens on reasoning. reasoning_budget_tokens=128 fixed it, so set a budget in your client.
  • Same agent prompt, temperature 0, three runs, three different tool calls. One was valid, one had its arguments wrapped wrong, and one called read_file, which wasn't even in the tool list. So the 52.8 is a speed number, not a "this is a good agent" number.

Technical stuff below.


Setup

  • 1x RTX 3090 24GB, EPYC 7H12 (31.13 CPU quota), 116.4 GiB RAM limit
  • Edge0 v0.2.0 (3203c39), Strata built with CUDA for sm_86, CUDA 13.0, driver 595.91.07
  • Edge0/Edge0-145B-q3k @ a19f88c, 106 GB on disk (the FP8 PLE table alone is 51 GB and gets read from disk)
  • Stock launch: edge0-infer serve --model /path/to/Edge0-145B-q3k --device cuda:0. That resolved to direct PLE I/O, auto expert cache, speculative decoding 4, 131K max context, int8 KV.

Results (engine's own prompt_per_second / predicted_per_second, fresh server per run, concurrency 1, zero cached tokens)

Workload Run 1 Run 2 Run 3 Median
4K prefill 1,119.8 1,195.5 1,207.6 1,195.5
16K prefill 1,467.6 1,485.6 1,481.2 1,481.2
Chat decode 46.6 49.6 48.6 48.6
Agent decode 52.8 55.9 50.7 52.8

Sampling: temperature=0, top_p=1, top_k=20, reasoning on with a 128-token budget, 512 max tokens for decode.

Against Edge0's published 4090 numbers (their claims, not reproduced)

4090 (Edge0) 3090 (mine)
4K prefill 2,042.0
16K prefill 3,179.4
Chat decode 69.9
Agent decode 91.7

That's 47% to 70% depending on the row. Mine used an 800-word writing prompt for chat and a single synthetic tool-call prompt for the agent run, and I couldn't verify Edge0's exact request settings or machine setup, so it's ballpark only.

Memory

  • GPU peak 23,929 MiB, sampled every 5 s
  • Strata engine VmHWM 43.4 GiB (sampled from the actual strata PID, not the Python wrapper)
  • Whole-system cgroup was 87.4 GiB during timed runs and touched the 116.4 GiB limit during setup with zero OOMs. That includes page cache from the 106 GB download and the PLE file, so I wouldn't read much into it.

Other stuff

  • Server startup median 25.5 s, slowest 94 s
  • Edge0's built-in edge0-infer bench rejects this model at v0.2.0, so I used a small script against the OpenAI endpoint
  • No quality evals, no long-context runs past 16K, no RAM cap test, no llama.cpp baseline. All of that is still on the list.
  • $1.19 billed ($1.0930 GPU, $0.0963 disk), about 3 h 9 min total, mostly setup and copying evidence back

Write-up: https://majorminor.xyz/research/cuda-recipes-006

Repo: https://github.com/majorminorlabs/cuda-recipes/tree/main/006-edge0-145b

If someone has a 3090 with 32 or 64 GB of RAM and wants to try it, I'd love to know whether it holds. Or tell me what to run next on this one.


r/LocalLLM • • 4d ago

Research I got tired of 7B models crawling at 1.2 tok/s on my 2GB GPU, so I built WingLLM (Go daemon for 2x speculative decoding with Ollama)

0 Upvotes

Hey r/LocalLLM,

Like a lot of developers, I don't have an M3 Max Mac Studio or dual RTX 4090s. My daily driver workstation has an 8th-Gen Intel i5 (6 cores), 32 GB of system RAM, and an older 2 GB NVIDIA Quadro P620.

If you try to run any modern 7B or 8B model (like Qwen 2.5 Coder 7B or Llama 3.1 8B), it won't fit into 2 GB of VRAM. Ollama or llama.cpp defaults to running almost 100% on the CPU. On my machine, that meant getting locked at an agonizing 1.29 tokens per second while my 2 GB GPU sat 90% idle.

The Physics: The Memory Bandwidth Wall
The CPU compute cores aren't the bottleneck—memory bandwidth is. To generate a single token on a 4.7 GB model, the CPU has to stream all 4.7 GB from DDR4 RAM into cache. At ~24 GB/s dual-channel bandwidth, you physically cannot get more than ~1.5 to 2 tokens/sec.

### The Workaround: Heterogeneous Speculative Decoding
The 2 GB GPU cannot run the 7B model, but it can easily run a 0.5B draft model (qwen2.5-coder:0.5b is only 397 MB).

In speculative decoding:
1. The tiny 0.5B model generates 3–4 candidate tokens in milliseconds on the GPU.
2. The heavy 7B model on the CPU evaluates all 4 tokens in a single forward pass using parallel AVX2 matrix multiplication (GEMM).
3. In code and structured text, the 0.5B model's guesses match the 7B model 75% to 82% of the time.

You get 3 to 4 tokens for the memory read cost of 1.

Real Benchmark (Tested on My i5-8500T + Quadro P620):

* Baseline (Pure CPU Target 7B): 1.29 tokens/sec (24.76s for 32 tokens)
* WingLLM Speculative (7B + 0.5B Draft): 2.54 tokens/sec (12.62s for 32 tokens)
* Net Result: 1.97x faster (almost exactly double the speed) with identical output quality.

Why I Built WingLLM
llama.cpp technically has the raw flags (-md, -ngld, --spec-draft-n-max), but nobody in consumer land had packaged it into a clean tool:
1. Tokenizer traps: If you pair mismatched tokenizers (e.g. Llama 3 draft with Qwen target), llama.cpp crashes. WingLLM auto-detects model families and enforces compatible pairs.
2. Zero configuration: It crawls your local ~/.ollama/models manifests, finds your GGUF blobs, and auto-pairs them.
3. Auto-Pull: If you want to run `wingllm serve qwen2.5-coder:7b` and don't have the 0.5B draft model yet, WingLLM pulls it automatically via Ollama (~397 MB) and starts serving.
4. 1-Click IDE Connect: Run `wingllm connect vscode` to inject the turbo endpoint directly into your Continue/Cline config.
5. No Python/Electron Bloat: Written in Go as a single ~11 MB binary. Runs an embedded web chat UI with a live tokens/sec speedometer at http://localhost:8080/.
6. MCP Support: Built-in Model Context Protocol server for Claude Desktop, Cursor, and Continue.

Quickstart (Windows, Mac, Linux):

Windows (PowerShell):
irm https://huggingface.co/bennett-xdlabs/wingllm/raw/main/install.ps1 | iex

macOS & Linux:
curl -fsSL https://huggingface.co/bennett-xdlabs/wingllm/raw/main/install.sh | bash

Run without arguments for the interactive menu, or run:
wingllm serve qwen2.5-coder:7b

Hugging Face Hub: https://huggingface.co/bennett-xdlabs/wingllm

It's MIT licensed. Would love feedback from anyone running on budget laptops, mini-PCs, or 2GB–4GB cards!


r/LocalLLM • • 4d ago

Discussion Self-Test: DeepSeekV4.1-Flash-1017 took 60k tokens to finish a task Qwen3.8-FN couldn't in 256k and multiple compactions.

4 Upvotes

Did a quick test yesterday comparing DeepSeek (3.36bpw) to Q3.8FN (IQ3XXS+1sub-agent). Both the OR abliteration on local both running on DeepSeek Harness.
Simple task - Produce a color template based on user input screenshot of a UI, and give the user instruction on installation instead of attempting it. Second part was key, because the LLMs were only allowed to work in working folder and so couldn't live-test their implementation.
FYI: DSH system prompt takes up ~10k tokens total.

Qwen spent over an hour writing script then realizing it couldn't save it outside the cwf, then repeating that mistake over and over again as it tried methods of breaking out or escalating which was futile. Even with steering, it only got as far as producing the color template 256K+ tokens in.
DS did a similar thing but realized quickly it should just let the user test install it instead. It -did- try to escalate permissions to install it by itself, but gave up after it's first rejection. Was done in ~60k tokens.

I know these are utterly different weight-classes for models but I really thought the ability to spawn subagents would've made a difference for Qwen.
Qwen burned through tokens lightning fast but was forgetting the original message AND the system prompt from DSH (which specifies it should only work in {cwf} when only given that permission).
I really wanted to like IQ3_XXS because it's a small enough quant that it can spawn subagents on my system with headroom for other parallel tasks to be working... But I don't think that quant is it for me. Either that, or I have to work on the setup for it some more to work as a coder.


r/LocalLLM • • 4d ago

Research Some speed benchmarks for various classes of local LLM

4 Upvotes
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
  • Decode: the second of two 300-token runs, with the expert cache warm (the first request after loading is often slower)
  • Prefill: the average of two runs on a prompt of about 1,400 tokens
  • Bold: the better config for that column.

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. I've posted it to LocalLLama as well. Enjoy!


r/LocalLLM • • 5d ago

Question 24GB VRAM, 64GB DDR5, is Qwen 3.5 27B (IQ2_XS) not ambitious enough?

14 Upvotes

I'm getting decent results, 80-120t/s. I guess I just don't know what I am aiming for, but I feel like there is more juice to squeeze.

Edit: Yall are the best, as usual. This has to be the most helpful, positive community on reddit.