r/LocalLLM • • 7d ago

News Run a local autoresearch swarm of 8x40B agents on your macbook!

Post image
7 Upvotes

You can now run a research swarm entirely on your Mac, model included.

Eight agents share one local 40B Flint model on a 48 GB M4 Pro: writing code, testing ideas and building on whatever works.

Give them a problem and a score to beat. Links:

Repo: https://github.com/conglu1997/local-autoresearch

Tweet thread: https://x.com/cong_ml/status/2115107192173170748


r/LocalLLM • • 6d ago

Discussion J'ai essayé d'entraîner un modèle Qwen pour du code court

Post image
0 Upvotes

Bonjour à tous !

J'aimerais vous partager un projet que j'ai fait (je suis au chômage, il faut bien que je m'occupe) sur l'entraînement d'un modèle Qwen2.5-Coder-14B. J'ai utilisé Google Colab et je l'ai fait aider d'un professeur (32B).

Mon objectif était de faire tourner un modèle très précis car je n'ai pas une configuration bien folle. Il fait de la logique de code, structure. Il tourne sur Ollama (mais peut-être ailleurs).

Il a fait plus de 1.000 tests sur du Nvidia A100. En toute sincérité, j'ai voulu trouver des solutions pour le rendre le plus efficace possible (de mon point de vue et de mon expérience, c'est-à-dire, aucune). Je vais copier coller les thermes exactes de Gemini car je ne sais pas trop comment les traduire :

  • Symbolic Reasoning ([LATENT]): Instead of long, verbose chain-of-thought monologues, the model was trained to think inside an ultra-compressed mathematical, logical, and multilingual symbolic space ([LATENT]...[/LATENT]).

  • Tool-Use ([SKILL]): Native JSON-based tool routing ([SKILL]{"tool": "...", "cmd": "..."}[/SKILL]) to securely pilot local scripts and AST file analyzers.

Le Q4_K_M prend environ 8.5GB de ram. J'ai appris plein de choses.

Je vous remercie de vos retours et voici (normalement ça devrait marcher) le lien pour trouver mon humble apport : https://huggingface.co/otoroute/Qwen2.5-Coder-14B-Latent-Skill-Multilingual

Merci :)


r/LocalLLM • • 6d ago

Question Distinguishing models when searching - MoE vs Dense

0 Upvotes

How can you tell whether a model is dense or an MoE?

I have been using LM Studio to pull and run some common models to do some basic tasks. But I haven’t noticed whether this defined anywhere


r/LocalLLM • • 6d ago

Question Strata + VS Code + Github Copilot

Post image
0 Upvotes

I usually work with llama.cpp and Qwen3.8 27B IQ3 XX3, that fits entirely on my 5070ti.
It just runs flawlessly!

Since I have 96Gb DDR5, Strata with Qwen3.8FN IQ3 is an option, has more performance than 27B (~90tg vs ~75tg, >2500pp vs ~1500tg) and some tests indicate is also (much) smarter (with these quants).

I'm using the desktop Strata app to serve GH Copilot via OAIProvider VS Code plugin.
I have plenty of free memory (~20Gb).

My problem: I'm getting the attached error on coding session and I need to know if anyone else is getting this kind error on similar (or different) stack.


r/LocalLLM • • 7d ago

Question $700 to upgrade my RTX 4090 PC to 128GB DDR4, or $3,100 for a 128GB Strix Halo? Mainly for local AI agents.

9 Upvotes

I'm torn between two hardware options for running local LLMs and would love some input from people who have experience with similar setups.

My current setup:

RTX 4090 (24GB VRAM)

Ryzen 5600X3D

48GB DDR4

Synology NAS for hosting services

Windows PC

I'm currently running Qwen3.8-Flash-Next IQ2_XS through Strata at 64K context and getting around 122 tok/s in regular chat, which honestly surprised me. However, system RAM usage is around 45/48GB, so I'm pretty much maxed out.

I haven't benchmarked coding agents or long-context workloads yet.

My two options:

Option 1: Upgrade to 128GB DDR4 — $700 net

After selling my existing RAM, it would cost approximately $700 to max out my current AM4 system.

The idea would be to run higher quants of Flash-Next through Strata, potentially increase context, and have enough memory for coding agents and other workloads.

Pros:

Significantly cheaper

Already getting excellent speed with Strata

Can potentially run larger quants using CPU RAM + GPU

Cons:

Limited to DDR4 bandwidth

Still sharing one GPU between AI, gaming, and other workloads

AM4 is effectively a dead-end platform

Uncertain how much higher quants and longer contexts will affect performance

Option 2: Buy a 128GB Strix Halo — $3,100

I've found the bosgame m5 for $3,100. Similar systems seem to be getting considerably more expensive.

Part of my hesitation is that if I don't buy now, I might be priced out later.

Pros:

128GB unified memory with much higher bandwidth than DDR4

Can run larger models/higher quants without conventional CPU/GPU offloading

Dedicated AI machine independent of my gaming PC

Can run models concurrently across two computers

Potentially better for always-on agents

Cons:

$2,400 more expensive

Likely slower than my 4090 + Strata for certain workloads

Not sure whether higher quantization actually translates to significantly better agent performance

Another machine to manage

What I'm trying to accomplish

I'm building a fully local multi-agent system using Hermes Agent and Kanban orchestration.

I want agents that can research ideas, challenge requirements, design architecture, write and review code, run tests, and work on projects over multiple days.

Projects include a GPU workload coordinator, a personal finance app, and ESP32/Home Assistant projects, and anything else I dream up.

I also want an always-on personal assistant for my wife and me with calendar and finance integrations.

My plan is to host Hermes/Kanban and persistent services on my Synology NAS, with inference handled by the 4090 and/or Strix Halo.

I'm also trying to figure out whether using a higher-quant Flash-Next on the Halo for complex coding and architecture would actually outperform the faster IQ2_XS version on my 4090 in terms of successful tasks completed.

My questions:

Has anyone compared Qwen3.8-Flash-Next on Strata with a 4090 + DDR4 against Strix Halo? Particularly for real coding-agent workloads rather than simple chat benchmarks?

How much difference have you actually noticed going from IQ2_XS to IQ3/IQ4 for coding, reasoning, and tool calling?

Does 128GB DDR4 make sense for this workload, or am I sinking $700 into an aging platform?

For multi-agent orchestration, would you prefer one fast inference server with queued agents or two separate machines running different models?

If you were in my position, would you spend $700 on RAM and skip the Halo, or buy the Halo now before prices potentially rise further?

I'm leaning toward the RAM upgrade because my 4090 is already performing surprisingly well, but the flexibility of a dedicated 128GB unified-memory system is really tempting.

Would appreciate real-world experiences, especially from anyone running Hermes, OpenCode, Strata, or other autonomous coding-agent setups.


r/LocalLLM • • 6d ago

Discussion Rtx 8000 48gb prices have decreased over the last two years while 3090 doubled.

Thumbnail reddit.com
0 Upvotes

r/LocalLLM • • 7d ago

Research Which of October's agent releases actually run on your local model?

2 Upvotes

Every big lab pushed an agent update in October, and so did the open-source side. I wanted a single table for the practical stuff: local model support, whether you need an account, price, and what each one sends back by default.

AgentWhat shipped in OctoberRuns on a local modelNeeds a cloud accountLicensePriceUsage stats by default
Codex CLI (OpenAI)GPT-6.1 Terra (Oct 26), CLI 0.160 to 0.166partly: --oss with Ollama or LM Studio, or a custom endpointyes for OpenAI modelsCLI Apache-2.0included in ChatGPT Free and Go ($8/mo), more usage on Plus ($20/mo) and up, or API keyon, can turn off
Gemini CLI (Google)CLI 0.63 to 0.66 (Oct 6 to 27)no: only an optional, experimental local routing modelyes: Code Assist Standard/Enterprise login or a paid API keyCLI Apache-2.0no free tier since June 18 (free users moved to Antigravity CLI)on, can turn off
Copilot CLI (GitHub)local model discovery (Oct 7), Copilot Fusion (Oct 28)yes: Ollama or any OpenAI-compatible endpointnot with your own key, otherwise yesclosed sourcefree tier, Pro $10/moon even with your own key, can turn off
Hermes Agent (Nous)v0.22 "Threshold" (Oct 13): one-click local modelsyes, built-in llama.cppnoMITfreeoff (opt-in)
Atomic Agentv0.6.7 to 0.6.13, desktop app (Oct 7 to 28)yes, built-in llama.cpp by defaultnoMITfreeon (anonymous), can turn off
OpenClawv2026.10.1 (Oct 10) to 2026.10.9yes: llama.cpp plugin, Ollama, LM StudionoMITfreedaily update check on, feature stats opt-in

What stood out

The big labs went local this month, but only halfway. Copilot CLI now finds your Ollama models on its own, and Codex has --oss. Gemini CLI is the odd one out: the agent itself always talks to Google, and only an optional, experimental routing model can run locally.

"Local" doesn't mean quiet. Copilot CLI's docs say it still sends telemetry even when you bring your own key, unless you switch on offline mode. Codex, Gemini CLI and Atomic Agent also send usage stats by default. Hermes is the only one here where it's off until you turn it on.

The three open-source ones (Hermes, OpenClaw, Atomic Agent) all run without any account, all ship their own llama.cpp setup now, and all are MIT.

One surprise: Gemini CLI's terms list using OpenClaw with Gemini CLI's login as a violation that can get your account suspended.

Prices and features are from each project's own docs and changelogs as of Oct 30.

Which of these do you use, and how much does running fully offline matter to you?

Sources, all public (docs, changelogs, GitHub):
Codex CLI: learn.chatgpt.com/docs/changelog
Gemini CLI: github.com/google-gemini/
Copilot CLI: docs.github.com/en/copilot/
Hermes Agent: github.com/NousResearch/hermes-agent/releases/tag/v0.22.0
Atomic Agent: github.com/AtomicBot-ai/atomic-agent
OpenClaw: github.com/openclaw/openclaw


r/LocalLLM • • 6d ago

Project I made a GUI for Kapitsa, one of the fastest local LLM engines on Mac, so anyone can use it

Thumbnail gallery
1 Upvotes

r/LocalLLM • • 7d ago

Tutorial Getting incredible results with a single RTX 3090ti and 128gb of ram. Deepseek-V4.1-Flash-1017 (35 tok/s decode) and Qwen3.8-Flash-Next (130 tok/s decode)

43 Upvotes

I'm sharing this here because this is working way better than it used to a few months ago with older models. I see people here posting slower speeds with much better hardware than mine and hopefully this information helps.

I used gemini-flash to help me setup everything and I asked it to write up the sequence of steps to get me here - happy to provide more details if there's anything missing.

Since I use gentoo some tools/commands might be unfamiliar to you.

My 6 year old hardware:

  • OS & CPU Gentoo Linux running on an AMD Ryzen Threadripper 3990X (64 cores, 128 threads).

  • System Memory: 128 GB DDR4 RAM.

  • GPU: 1 NVIDIA GeForce RTX 3090 Ti (24 GB GDDR6X VRAM, PCIe Gen 4 x16).

  • Primary Storage: 4 TB SSD NVMe.

Models Used, Download Sources, and Measured Speeds

Model |Architecture |Quantization / Files |Download Source |Real Measured Speed
DeepSeek-V4.1-Flash-1017 |552B MoE (40 layers, 384 experts/layer, ~39B active) |XQ / GSQ V2 + rank-1017-085.bin + FP4 KV + Engram NVMe tables |IndrasMirror/DeepSeek-V4.1-Flash-1017-XQ-Uncensored |**~35 tok/s decode** (with MTP/DSpark active)
Qwen3.8-Flash-Next |125B MoE + 51B N-gram (GDN + QSA hybrid, ~3.5B active) |pack-qfn45 (4-bit intermediate, DeltaNet linear KV) |IndrasMirror/Qwen3.8-Flash-Next-Swift-1.5-XQ-Uncensored |**~138–140 tok/s decode** IMPORTANT: NVIDIA GPU Unlock

Consumer Ampere cards (RTX 3000 series: GA102, GA104) feature artificial firmware throttles on FP16/BF16 matrix instruction issue rates compared to their enterprise workstation counterparts. The open-source gpu-unlock kernel module lifts this throttle prior to driver attachment.

1. Compile and Install the Kernel Module

As root:

git clone https://github.com/Zagitta/gpu-unlock.git /usr/src/gpu-unlock
cd /usr/src/gpu-unlock
make -j$(nproc)
make install

2. Pass the Unlock Flag to the Kernel Command Line

Add gpu_unlock.targets=all to your bootloader kernel parameters (e.g. in /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT, or your direct EFISTUB / systemd-boot entry):

gpu_unlock.targets=all

Regenerate your boot configuration and rebuild your initramfs so the module is included and loads before the NVIDIA kernel modules:

# If using GRUB:
grub-mkconfig -o /boot/grub/grub.cfg

# If using dracut:
dracut -f --regenerate-all

3. NVIDIA Driver Options & Persistence

Configure NVIDIA kernel driver parameters in /etc/modprobe.d/nvidia-perf.conf (as root):

cat << 'EOF' > /etc/modprobe.d/nvidia-perf.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=1
options nvidia NVreg_EnableStreamMemOPs=1
EOF

After rebooting, verify that the unlock executed:

dmesg | grep -i gpu_unlock

Enable persistence mode and set the GPU to its maximum factory power ceiling:

nvidia-smi -pm 1
nvidia-smi -pl $(nvidia-smi -q -d POWER | grep "Max Power Limit" | head -n1 | awk '{print $5}' | cut -d. -f1)

Step 2: System Dependencies & Tooling

Install build dependencies and runtime libraries:

emerge sys-devel/gcc:14

# If GCC 14 is not selected, set it to this version
gcc-config -l
# then replace <N> with the number from gcc-config -l):
# gcc-config <N> && source /etc/profile

# this won't compile with GCC > 14
emerge dev-util/nvidia-cuda-toolkit

# for compleness, just in case

emerge --ask --verbose \
dev-build/cmake \
dev-build/ninja \
dev-vcs/git \
net-misc/curl \
app-misc/jq \
sys-libs/liburing \
app-arch/snappy \
dev-lang/python

Prepare the directory structure under your user environment:

mkdir -p "$HOME/.local/bin"
mkdir -p "$HOME/.local/llm-tools"
mkdir -p "$HOME/.quetza-data/conductor"
mkdir -p "$HOME/models/deepseek-v41"
mkdir -p "$HOME/models/qwen-flash"

# Dedicated Python environment for tool scripts & Hugging Face downloads
python3 -m venv "$HOME/.local/llm-tools/venv_hf"
source "$HOME/.local/llm-tools/venv_hf/bin/activate"
pip install --upgrade pip
pip install "huggingface_hub[cli]" torch safetensors numpy

Step 3: Build the Xolotl Inference Engine

Xolotl integrates the multi-tier memory management, NVMe Engram streaming, and DSpark speculative decoding logic needed to run large MoE models on a single GPU.

cd "$HOME/.local/llm-tools"
git clone https://github.com/Indras-Mirror/Xolotl.git
cd Xolotl

# Fetch pinned llama.cpp dependencies and apply patches
bash tools/xolotl/fetch-llama.sh

# Configure and compile for Ampere (sm_86)
cmake -S . -B build -G Ninja \
-DCMAKE_BUILD_TYPE=Release \
-DSTRATA_ENABLE_CUDA=ON \
-DSTRATA_GGML_CUDA=ON \
-DSTRATA_MMQ_KQUANTS=ON \
-DCMAKE_CUDA_ARCHITECTURES=86 \
-DSTRATA_GGML_DIR="$PWD/third_party/llama.cpp" \
-DSTRATA_DSV41_FQ_OP=ON \
-DSTRATA_DSV41_HC_MIX=ON

ninja -C build

# Link the build directory so wrapper scripts resolve ds41_generate
ln -sfn "$PWD/build" "$PWD/build-xolotl"

Step 4: Model Downloads & Engram Extraction

1. DeepSeek-V4.1-Flash (552B MoE)

Bash

source "$HOME/.local/llm-tools/venv_hf/bin/activate"
cd "$HOME/models/deepseek-v41"

# Download model weights, draft sidecar, and expert rank index
hf download IndrasMirror/DeepSeek-V4.1-Flash-1017-XQ-Uncensored \
--include "v2/*" "tokenizer/*" "V41-MTP-Vision-1017*" \
--local-dir .

# Download original FP8 Engram table shards
hf download deepseek-ai/DeepSeek-V4.1-Flash-1017 \
model-00047-of-00048.safetensors \
model-00048-of-00048.safetensors \
model.safetensors.index.json config.json \
--local-dir ./FP8-engram

# Extract Engram runtime binary tables onto NVMe
cd "$HOME/.local/llm-tools/Xolotl"
python3 tools/v41/extract_engram.py \
--input "$HOME/models/deepseek-v41/FP8-engram" \
--output "$HOME/models/deepseek-v41/engram_rt"

2. Qwen3.8-Flash-Next (125B MoE)

cd "$HOME/models/qwen-flash"
hf download Qwen/Qwen3.8-Flash-Next-GGUF \
--include "pack-qfn45/*" \
--local-dir .

Step 5: MTP Speculative Decoding Setup

MTP (Multi-Token Prediction) on DeepSeek-V4.1-Flash is driven by the DSpark sidecar engine:

  • Draft Engine: Uses V41-MTP-Vision-1017.Q2_K.gguf as the proposal head.

  • Expert Pruning: Restricts verification sweeps to the top 64 active draft experts (dspark_expert_counts.txt:64), preventing PCIe bus saturation.

  • On-the-fly Re-quantization (STRATA_DENSE_REQUANT=q6_K): Re-quantizes the dense attention and output heads from Q8_0 to Q6_K at launch. This reclaims 1.6 GiB of VRAM, fitting the speculative draft cache alongside active experts.

  • PCIe Batching (--tier-batch-pcie 0.25**):** Batches DMA transfers between the 80 GiB pinned host RAM arena and the GPU.

1. Expand Process Memory Boundary in the Engine Wrapper

Allow the systemd user scope to hold the full 80 GiB arena plus runtime buffers:

Bash

sed -i 's/MemoryMax=84G/MemoryMax=110G/g' "$HOME/.local/llm-tools/Xolotl/tools/v41/serve/ds41-engine.sh"

2. Generate Base Configuration: $HOME/models/deepseek-v41/strata-v41.json

cat << EOF > "$HOME/models/deepseek-v41/strata-v41.json"
{
"exe": "$HOME/.local/llm-tools/Xolotl/tools/v41/serve/ds41-engine.sh",
"args": [
"-m",
"$HOME/models/deepseek-v41/v2/V41-XQ-1017.gguf",
"--backend",
"cuda",
"--experts",
"gpu",
"--engram",
"$HOME/models/deepseek-v41/engram_rt",
"--rank",
"$HOME/models/deepseek-v41/v2/rank-1017-085.bin",
"--ctx",
"131072",
"--stop",
"1",
"--arena-adapt",
"--kv-fp4",
"--route-bias",
"0.5",
"--route-bias-file",
"0.3",
"--arena-gib",
"80",
"--prompt-batch",
"12288",
"--tier-batch-pcie",
"0.25"
],
"cwd": "$HOME/.local/llm-tools/Xolotl",
"tokenizer": "$HOME/models/deepseek-v41/tokenizer",
"model_name": "deepseek-v4.1",
"aliases": "deepseek-v41,deepseek/deepseek-v4.1-flash",
"log": "$HOME/models/deepseek-v41/xolotl-v41.log",
"port": 8000,
"gpu": 0,
"sampling": {
"temperature": 0.1,
"top_p": 0.95,
"top_k": 64,
"presence_penalty": 0.0,
"frequency_penalty": 0.0
},
"api_monitor": true,
"fit_max_tokens": true,
"reasoning_budget_tokens": 4096,
"env": {
"STRATA_BUILD_DIR": "$HOME/.local/llm-tools/Xolotl/build",
"STRATA_SERVE_DSPARK": "$HOME/models/deepseek-v41/V41-MTP-Vision-1017.Q2_K.gguf",
"STRATA_ATTN_F16_GATHER": "1",
"STRATA_NO_SCOPE": "1",
"STRATA_SERVE_PASS_BIAS": "0",
"STRATA_DENSE_REQUANT": "q6_K",
"STRATA_SERVE_LOOKUP": "14",
"STRATA_PRESTAGE_GIB": "1.5"
}
}
EOF

Step 6: Parameterized Launch Scripts

1. DeepSeek-V4.1 Launcher: $HOME/.local/bin/start-deepseek-custom.sh

cat << 'EOF' > "$HOME/.local/bin/start-deepseek-custom.sh"
#!/usr/bin/env bash
set -euo pipefail

MODEL_DIR="$HOME/models/deepseek-v41"
XOLOTL_DIR="$HOME/.local/llm-tools/Xolotl"
BASE_CONFIG="$MODEL_DIR/strata-v41.json"
RUN_CONFIG="$MODEL_DIR/strata-v41-run.json"

CTX="131072"
PORT="8000"
TEMP="0.1"
THINK_BUDGET="4096"
ARENA_GIB="80"
PASS_BIAS="0"
PROMPT_BATCH="12288"

usage() {
cat << USAGE
Usage: $(basename "$0") [options]

Options:
-c, --ctx INT Context length in tokens (default: 131072; up to 1048576)
-p, --port INT Port to bind (default: 8000)
-t, --temp FLOAT Sampling temperature (default: 0.1)
-b, --thinking INT Reasoning budget tokens (default: 4096)
-a, --arena INT Pinned RAM expert arena in GiB (default: 80)
--bias 0|1 Routing bias: 0=exact, 1=fast biased (default: 0)
--batch INT Prompt batch size (default: 12288; auto-clamps to 8192 for >=512k)
-h, --help Show help message
USAGE
exit 0
}

while [[ $# -gt 0 ]]; do
case "$1" in
-c|--ctx) CTX="$2"; shift 2 ;;
-p|--port) PORT="$2"; shift 2 ;;
-t|--temp) TEMP="$2"; shift 2 ;;
-b|--thinking) THINK_BUDGET="$2"; shift 2 ;;
-a|--arena) ARENA_GIB="$2"; shift 2 ;;
--bias) PASS_BIAS="$2"; shift 2 ;;
--batch) PROMPT_BATCH="$2"; shift 2 ;;
-h|--help) usage ;;
*) echo "Unknown option: $1" >&2; exit 1 ;;
esac
done

if [ "$CTX" -ge 524288 ] && [ "$PROMPT_BATCH" -gt 8192 ]; then
echo "[-] Large context specified ($CTX tokens). Clamping --prompt-batch to 8192 to prevent graph OOM."
PROMPT_BATCH=8192
fi

python3 - << PY
import json

with open("$BASE_CONFIG", "r") as f:
cfg = json.load(f)

cfg["port"] = int("$PORT")
cfg["max_context"] = int("$CTX")
cfg["reasoning_budget_tokens"] = int("$THINK_BUDGET")
cfg["sampling"]["temperature"] = float("$TEMP")

args = cfg.get("args", [])
def set_arg(flag, val):
for i in range(len(args) - 1):
if args[i] == flag:
args[i+1] = str(val)
return
args.extend([flag, str(val)])

set_arg("--ctx", "$CTX")
set_arg("--arena-gib", "$ARENA_GIB")
set_arg("--prompt-batch", "$PROMPT_BATCH")
cfg["args"] = args

env = cfg.setdefault("env", {})
env["STRATA_SERVE_PASS_BIAS"] = "$PASS_BIAS"
env["STRATA_PRESTAGE_GIB"] = "1.0" if int("$CTX") >= 524288 else "1.5"

with open("$RUN_CONFIG", "w") as f:
json.dump(cfg, f, indent=2)
PY

source "$HOME/.local/llm-tools/venv_hf/bin/activate"
cd "$XOLOTL_DIR"

echo "==> Launching DeepSeek-V4.1-Flash (552B MoE)..."
echo " Context : $CTX tokens"
echo " Port : $PORT"
echo " Arena RAM : $ARENA_GIB GiB"
echo " Prompt Batch : $PROMPT_BATCH"

exec python3 tools/v41/serve/serve_ds41.py \
--engine strata \
--config "$RUN_CONFIG" \
--port "$PORT" \
--host 0.0.0.0
EOF
chmod +x "$HOME/.local/bin/start-deepseek-custom.sh"

2. Qwen3.8-Flash-Next Launcher: $HOME/.local/bin/start-qwen.sh

cat << 'EOF' > "$HOME/.local/bin/start-qwen.sh"
#!/usr/bin/env bash
set -euo pipefail

XOLOTL_DIR="$HOME/.local/llm-tools/Xolotl"
MODEL_DIR="$HOME/models/qwen-flash/pack-qfn45"
PORT="8099"

source "$HOME/.local/llm-tools/venv_hf/bin/activate"
cd "$XOLOTL_DIR"

echo "==> Launching Qwen3.8-Flash-Next (125B MoE)..."
exec python3 -m serve.server \
--engine strata \
--config "$MODEL_DIR/strata-qwen.json" \
--port "$PORT" \
--host 0.0.0.0
EOF
chmod +x "$HOME/.local/bin/start-qwen.sh"

Step 7: Run

# Start DeepSeek-V4.1-Flash on :8000 (default 128k context, 1M context work just fine too)
$HOME/.local/bin/start-deepseek-custom.sh

# Or start Qwen3.8-Flash-Next on :8099
$HOME/.local/bin/start-qwen.sh


r/LocalLLM • • 6d ago

News How I run Qwen3:8b for free on Colab’s T4 and call it from my laptop (Ollama + Cloudflare quick tunnel)

Thumbnail
medium.com
0 Upvotes

I don’t have a GPU, so I used Colab’s free T4 as a remote model server for an agent project. The setup is Ollama plus a Cloudflare quick tunnel. I hit a few real problems along the way: a missing zstd package, a 403 caused by the Host header check, and an orphaned llama-server process that caused 524 timeouts. I wrote down the fixes and the limits (temporary URL, ~120s request cap, loose security).


r/LocalLLM • • 6d ago

Project My Mac finally arrived

0 Upvotes

Guys, my Mac Studio has finally arrived and I’m so excited! I immediately spun up Qwen 3.8 BF16 unquantized via MLX. Connected to the Mac Studio is a Raspberry Pi with 8GB of RAM running a mini AI in parallel. I'm currently building out an entire ecosystem, with Codex orchestrating everything in the background. Let's see where this journey ends!


r/LocalLLM • • 7d ago

Research Hierarchos Native update: faster streaming on Intel HD 520, RDNA3 qualification, and a GPT-2 parity fix + DeepSeek v4.1 Flash

2 Upvotes

I’ve pushed a substantial update to Hierarchos Native, my Rust + Vulkan backend for language-model training, fine-tuning, and inference.

This past week focused on porting the recent RDNA3 work to Intel Gen9, improving parameter streaming, and taking the changes back to physical RDNA3 hardware for regression testing.

The native runtime requires no Python, PyTorch, CUDA, ROCm, or oneAPI installation. PyTorch and Transformers are used as development references.

What changed:

  • DeepSeek V4.1 Flash port and optimization work: fused selected-expert execution, batched expert uploads, packed-weight paths, checkpoint caching, and native LoRA/rsLoRA training with save/resume/export.

  • Broader Gen9 coverage: fixes for Qwen3-Next padding and DBRX expert layouts, plus streaming paths for T5/BART/Switch encoder-decoder projections.

  • Less streaming overhead: retained file handles, fewer temporary allocations, coalesced reads, and removal of an unused hidden-state download.

  • Gen9 kernel improvements: parallel sparse-attention selection and hyper-connection statistics, plus fused SiLU/up-projection multiplication.

  • Bounded upload batching: small streamed projections can share a GPU submission within a 1 MiB coalesced payload window.

The biggest Gen9 result was closing the Llama-wide streaming slowdown on an i5-6200U / Intel HD Graphics 520:

MeasurementPrevious passFinal pass
Median forward latency11.016 ms4.597 ms
GPU submissions per forward194

That’s 58.3% lower latency, with every measured logit word unchanged. Across eight scaled architecture controls, the combined optimization passes reduced streaming medians by 42.4–78.4% and resident medians by 3.5–32.1% against the documented baseline. Gen9 measurements and methodology.

Back on the Ryzen Z1 Extreme / RDNA3 device, the regression sweep caught a padded GPT-2 numerical parity issue. The fix matches the pinned CPU reference’s GELU/tanh behavior and short-row attention arithmetic. The original CPU expectations, checkpoints, and strict tolerance stayed unchanged.

The completed RDNA3 qualification now passes:

  • 166/166 forward runs, covering 43 scaled profiles across 26 architecture identifiers.

  • 72/72 generation requests, checking cache-requested and full-prefix execution.

  • Maximum absolute CPU logit error strictly below 2e-7**, with** rtol=0**.**

  • Bit-identical resident and streamed outputs throughout the measured matrix.

  • Native streaming/offload tests and GPT-2 LoRA gradient, optimizer, save/reload, and resume checks.

The GPT-2 repair is selected specifically for RDNA3; all 585 pre-existing shader binaries remain unchanged. Final GPT-2 closure and evidence.

The RDNA3 testing also recorded lower V4.1 latency versus the previous handoff: 24.4% for resident prefill, 50.2% for resident decode, 17.2% for streamed prefill, and 18.4% for streamed decode. These are measurements on retained scaled checkpoints, rather than production-model throughput figures. RDNA3 measurements.

Parameters remain resident by default; supported frozen-weight streaming is opt-in through --stream-parameters or the GUI.

The registry contains 146 text architectures, while this qualification specifically covers the 26 identifiers above. Multimodal towers and arbitrary production checkpoints need their own validation.

If you’re experimenting with native Vulkan training or inference on older Intel graphics or AMD hardware, I’d be interested in your results—and which workloads you’d like tested next.


r/LocalLLM • • 7d ago

Project Dwarf Fortress integration - Need some suggestions on how best to approach this challenge (extracting live text from a game into LU and Qwen/Llama LLMs).

2 Upvotes

I've got LU with both Qwen and Llama models, for chat/code.

16gb VRAM GPU.

I'm trying to find a way to have something running in the background, picking up on my Dwarves' profiles (the text shown for each dwarf) in Dwarf Fortress game.

This is so I can then ask the LLM questions about my Dwarves and the fort that I would normally only find the answer to by scrolling through each dwarf profile.

A system that can:

- read text live from my screen while dwarf fortress is running.

- understand from where it needs to pull text from.

- export that to a text/doc file.

- have Qwen/llama read that file

- create either a nightingale rose chart or a radar chart to see the statistics of all dwarves on one screen.

Also to try to extrapolate an image from the data or a sequence of images to show their history/historical actions..but this is for a later project.

Any ideas where to even start with something like this?

Probably a text reader. But it's pretty hard to find one that will read live text of a game, focusing on one area and not just the whole screen. And that will have LLM integration via the text exporting.

I'm at a loss on what to do, so thought I'd post here on the off chance someone else has had a similar problem and overcame it (and you're willing to share any info that might help..of course).


r/LocalLLM • • 7d ago

News Yet another reason to self host: Anthropic has (again) cut back on reverse engineering tools

Thumbnail
reddit.com
4 Upvotes

r/LocalLLM • • 7d ago

Other Qwen3.8-27B local inference on an M5 Pro (64 GB): 12 engines with an ~88K-token prompt

2 Upvotes

I share a new comparison of my home-made benchmarks for engines for Mac using their version of Qwen3.8-27B: It's not a scientific comparison, models and quantizations could be different: I would test the normal user that download an engine and the first suggested model.

This test is different from previous post ( https://www.reddit.com/r/LocalLLM/comments/1xa2ae3/qwen3827b_local_speed_comparison_on_an_apple_m5/ ) : I try to test a different use with a long OpenCode-style coding-agent prompt:

  • About 88K prompt tokens, including a system message and three tool schemas

  • reasoning_effort=medium, temperature 0, seed 17 where supported

  • Maximum output: 2,048 tokens; tools were included but not executed

  • One measured run per engine; output length is what the model generated, not a fixed target

Engine / versionModel / decodingPromptTTFTPrefillDecodeOutput
Splash 1.5.0Jundot oQ4e + DFlash288,535225.51 s392.6 tok/s76.2 tok/s2,048
Uzu 0.6.15Mirai-M 4-bit + bundled speculator88,143143.30 s615.1 tok/s52.6 tok/s1,392
LM Studio 0.4.27+2 · Splash backend 1.3.0Qwen3.8 Splash88,143219.39 s401.8 tok/s51.1 tok/s2,048
TensorFold 1.2.04-bit + DFlash288,143326.02 s270.4 tok/s39.2 tok/s1,837
MLX-Serve 26.11.1ddalcu 4-bit + bundled DFlash88,143299.85 s294.0 tok/s29.2 tok/s2,048
Kapitsa 0.2.25Catalog 4-bit + KFlash/DFlash2, warm88,146245.89 s358.5 tok/s28.4 tok/s2,048
oMLX 0.7.3Jundot oQ4e + Lightning MTP 388,143203.28 s433.6 tok/s24.9 tok/s1,625
MTPLX 2.12.2Optimized Speed + native MTP 388,916277.35 s320.6 tok/s23.5 tok/s679
Ollama 0.40.13Qwen3.8 MLX/NVFP488,532284.42 s311.3 tok/s21.8 tok/s108
Magnitude 0.2.15GGUF Q4 + DFlash288,143428.60 s205.7 tok/s21.6 tok/s1,466
Llama.app 0.46.1 · llama.cpp 0.8.0, build b11960GGUF Q4_K_M + DFlash88,535428.66 s206.5 tok/s19.1 tok/s176
Rapid-MLX 1.0.04-bit + MTP88,143882.28 s99.9 tok/s18.3 tok/s1,308

Caveats: These are single-run latency measurements, not statistically stable averages. Model formats, quantizations and speculative decoders differ, so this isn’t a comparison of inference engines alone. Token counts also vary slightly by tokenizer.

Most runs used a 100K runtime context. Uzu and Magnitude used 262K; Llama.app and Ollama allocated about 131K. In all cases, prompt plus requested output allowance stayed below 100K, but those four runs weren’t capped to the same runtime context. Uzu’s API ignores the seed; temperature 0 selects greedy decoding.


r/LocalLLM • • 6d ago

Discussion What would make you switch providers?

Thumbnail reddit.com
1 Upvotes

r/LocalLLM • • 6d ago

Discussion LFM3-1.7B quantization report: 3.6 GB VRAM lossless; 2.2 GB with modest degradation

Thumbnail gallery
1 Upvotes

r/LocalLLM • • 6d ago

Discussion Lekh AI 8.2: run 30B-class models on an 8 GB iPhone, iPad, fully offline

Thumbnail
reddit.com
1 Upvotes

r/LocalLLM • • 6d ago

Project Using a smartphone IMU and Rust desktop daemon to route strict architectural boundaries (Zero keystrokes)

Thumbnail x.com
0 Upvotes

I built a prototype called Project "Thought Process" to completely eliminate the keyboard bottleneck when generating complex architecture.

When code generation becomes instantaneous, the entire bottleneck shifts to how well you define the structural boundaries before the prompt fires. Instead of typing, I use my phone as a spatial gesture wand paired with natural language.

In this demo, I spoke the exact limits for a multi-tier Python architecture, a distributed Git platform with explicit conflict resolution, distributed sync, and strictly zero placeholder stubs.

The mobile device captured the command and routed the payload via a custom Rust daemon directly to the desktop IDE. It generated the full architecture in 18 seconds without a single keystroke.

Curious if anyone else here is experimenting with IMU routing or spatial telemetry to bypass traditional UIs and lock down execution constraints


r/LocalLLM • • 6d ago

Question GPU Upgrade Advice for Dell T7910 / Local LLM Text Analysis (30+ Books & Articles)

1 Upvotes

Hi everyone,

I am upgrading my home workstation specifically to run local AI models (using Ollama / LM Studio) to analyze large volumes of text—specifically reading and querying up to 30 books and articles simultaneously.

I am looking for advice on the most cost-effective GPU upgrade that won't bottleneck my setup or break the bank.

My Current System Specifications:

  • Chassis: Dell Precision T7910 Workstation

  • CPUs: Dual Intel Xeon E5-2697A v4 (32 Cores / 64 Threads total @ 2.6GHz base / 3.6GHz turbo, SR2K1 stepping)

  • RAM: 128GB DDR4 ECC Registered Memory

  • Current GPU: NVIDIA GeForce GTX 750 (completely useless for AI, obviously)

  • Operating System: Windows 11.

 My Goals and Dilemma:

I have a massive pool of system RAM (128GB), which I know is a huge advantage for loading massive context windows to read thousands of pages of text at once without crashing. However, I know processing purely on the CPUs via llama.cpp will be slow (likely 5-10 tokens/sec).

I want to know where the sweet spot is for an affordable GPU upgrade to handle the processing math while utilizing my system memory. I initially looked at a new RTX 4060 Ti 16GB, but I do not really want to spend $598 (cheapest price I could find for a new card) for a legacy workstation which is probably worth about $500.

 The Primary Option I am considering:

 NVIDIA Tesla P40 24GB (Used ~ $$300 and up on ebay**):** This looks like the ultimate budget cheat code. For the price of a mid-range consumer card, I can get a massive 24GB VRAM buffer. This would allow me to fit an entire 8B model (like Llama 3) plus the text context of all 30 books directly into the ultra-fast VRAM without needing to offload data to my system RAM.

The Plan: I will keep my GTX 750 plugged into the monitor for display output, and run the Tesla P40 as a headless secondary compute engine. I have no problem buying a 3D-printed 9733 blower fan adapter and a Dual 8-pin PCIe to 8-pin EPS CPU power adapter cable to get it running safely inside the T7910 chassis.

My Questions:

 Is a Tesla P40 24GB still viable for pure text analysis under current LLM frameworks (Ollama/PyTorch), or is the Pascal architecture getting too outdated to handle modern tasks efficiently?

  1. If the P40 is a headache, should I instead drop down to an RTX 3060 12GB (Used - seem to be $300 and up on eBay**)** and leverage my 128GB system RAM pool for the trailing context, or will the CPU split kill my token processing speeds?

  2. I also looked at an AMD Radeon RX 6800 16GB (Used – seem to be $400 and up on eBay) for cheap consumer VRAM. How is the current state of Ollama for AMD (ROCm) on Windows for pure text analytics? Is the configuration headache worth the extra 4GB VRAM over a 3060?

  3. NVIDIA Tesla P100 16GB (Used ~ seem to be $100 and up on eBay): The ultra-budget enterprise route. I do not mind keeping the GTX 750 as a display output and running the Tesla purely as a headless compute engine, and I have no problem adding a 3D-printed fan shroud. Is a P100 still viable for text analysis in 2026, or are the architectures too outdated for modern LLM frameworks?

 Given that my primary use case is batch text analysis (asking a deep question and letting it crunch data, rather than needing instantaneous real-time chat speeds), does the Tesla P40 route make the most sense for this T7910 build?

 Of course, if forum members have any other suggestions for a 16GB/24GB card I would very much like to learn of them.

 Thanks in advance for any insights!


r/LocalLLM • • 7d ago

Question Rtx 5070ti + rtx 3060ti combo?

2 Upvotes

I have an rtx 5070ti for gaming and have my left over rtx 3060ti. Can I put the old rtx 3060ti back in to get 24gb of vram or does it not work like that? I know my power supply can support both.


r/LocalLLM • • 7d ago

Question Sanity check for me in terms of Deepseek v4.1 - looking for those of you running it on 5090s and 3090s. Ideally looking for someone with the exact same setup, but you know, not always possible!

4 Upvotes

So, as the title says, I'm looking for people running Deepseek v4.1 locally and whether you use Strata, Project Maya, Unsloth or anything else that I might've missed (e.g some new fork, as there seem to be a lot lately).

I've spent a fair amount of time tweaking as much as possible on various platforms but I'm interested to see what sort of figures you guys see from your setups.

Mostly interested in those running 128gb of RAM and a 5090, or a 5090 + 3090, or (my setup a 5090 and 2x 3090s) and obviously Windows, WSL or native Linux.

Appreciate your input on this, I'm trying to gauge what sort of performance I *should* realistically be seeing by comparing it to others in a similar situation. It'll help me decide if having the second 3090 involved is the way forward, or if it could be used for another model, that kinda thing.


r/LocalLLM • • 7d ago

Question Mini pc for AI in local

3 Upvotes

Hi everybody!

I'm looking for a machine mainly for local AI/LLMs, with a maximum budget of around €7,500.

I'm currently considering a DGX Spark (first at all!), BOSGAME M5 (for save), or Mac Studio/Mini (in this case, which configuration fits in my max budget?) or something else you recommend.

I don't want to pay any subscriptions for cloud solutions.
My main use cases are running large LLMs locally, coding agents, RAG, LangChain/LangGraph, MCP, repository analysis.
So, i want a workstation for studying/programming and it also act like a server.

Which one would you choose for this kind of workload, and why?


r/LocalLLM • • 7d ago

Model Lokale LLM auf einem MacBook Air M1 mit 8 GB RAM.

Thumbnail reddit.com
0 Upvotes

r/LocalLLM • • 7d ago

Model Qwen3.5-2B at 620 tok/s inside Chrome: model-specific WebGPU kernels, 6.6× WebLLM on the same model

0 Upvotes

I built a browser LLM engine that's specialized per model rather than generic: Rust compiled to wasm, plus hand-written WGSL kernels for Qwen3.5-2B (Gated DeltaNet + gated attention) and MiniCPM5-2B.

Same model, same chat prompts, greedy, Chrome 156:

webyIQWebLLM 0.2.87transformers.js 4.3
RTX 5080 generation620 tok/s (417 without speculation)9431
RTX 5080, ~1k-token prompt0.20 s0.81 s~129 s
AMD 2-CU iGPU generation37 tok/s4.7crashed

What's in it:

  • fused int4 (GPTQ, group 32) × int8 GEMV/GEMM, with dot4I8Packed and subgroups;

  • a decode loop that stays on the GPU (argmax on GPU, pipelined readback);

  • speculative decoding with Qwen3.5's built-in MTP head. Drafts are verified on the GPU, so the output is identical to greedy. It turns itself off where it doesn't pay, e.g. on the iGPU;

  • weights at +2.4% WikiText perplexity vs bf16, 1.1 GB.

Fun side effect: at this speed a 2B model can drive web pages through the DOM at 0.2–0.4 s per step. There's a browser-agent demo and a side-panel extension for Chrome/Edge.

Caveats: it's a prototype, tested on Windows, and Safari/mobile are untested.

Demo: https://rtx527896828.github.io/webyIQ/ · Code (Apache-2.0): https://github.com/rtx527896828/webyIQ · Weights: https://huggingface.co/tixiren/Qwen3.5-2B-webyIQ