Pinned Tweet
Somebody told me to get more power, so I did. Turns out a terabyte still doesn't fit in 128GB. But my $3,250 rig runs a 125B MoE at 77 tok/s flat across 2K-128K, 25% ahead of the vendor at depth. Arithmetic beats more power. What does your rig do at 128K? @gospaceport @coldniko
xitter.cf/HiredGunDevDen/status/…
The local AI community thanks you for your service!
I validated it, NVIDIA did leave a free 60% on the table for Ampere/Ada GPUs 😎
Quad 3090s + Qwen 3.8 27B BF16 in vLLM:
Unpatched: 1114–1259 tok/s prefill
Patched: 1769–2020 tok/s prefill
FREE ~60%+ on prompt processing from 2K all the way to 128K. About 15 mins shaved off every hour for long running agentic tasks in Qwen 3.8 27B and other full precision dense models.
Decode, the same. Power utilization, the same. 🔥 risk, the same.
Quantized models + Imgen/Vidgen, testing soon to get hard numbers
Windows unlocked as well. 50X0, probably 🔜
Kernel module, no driver patching or vbios crap.
Easiest free win of the year for Local Ai 🎉
Notes + bench script: digitalspaceport.com/gpu-unl…
Anyone else got their AI/SI system structured like a company? @gospaceport @SpaceXSI @NousResearch @coldniko @NetworkChuck @QwenDevs
I think my AI rig is ~3K after all the upgrades I can make for my little B550 (128G DDR4, Risen 9 5900XT, 3 5060TI cards, 500G NVMe)... I spend less than ~100 a year in frontier tokens and I am pushing ~ half a million lines of code shipped. themightyjoshua.com
I ran this on 32Gb DDR4 and a Risen 5 5500 before the upgrades last month.
Unless of course @coldniko has a list of features he wants built by the community.
Awesome
Engineers. How do you use Agents? I'm not asking for how they work. I'm asking your method for building and choosing the brain they run on.
This is what drove me to local AI. Never paid Claude but grok does the same thing. I've learned if you use DeepSeek v41 and grok as sub agents and local as your main life is much much better. Local holds your project and rag proper like and if you need extra umph DeepSeek for DeepSeek and grok is more than enough at a tenth the expense.
REALLY good advice.
"1. Make your requirements less dumb. Everyone is wrong no matter who you are some of the time.
2. Try very hard to delete the part or process. If you aren't occasionally adding things back in you aren't deleting enough.
Whatever requirement or constraint you have you must have a name attached.
3. Simplify/Optimize: Most common problem in engineering is to optimize something that shouldn't exist.
4. Accelerate Cycle time: your moving too slowly, go faster, but don't go faster until you fix 1-3.
5. Automate" -- @elonmusk
Had to issue a correction to my last post! Realized I botched my tests which threw off some of my results and thus, the major conclusion I reached. @coldniko @gospaceport
If you have time, come check out my labor of love. This chess site was built by myself, using my Local AI. @gospaceport @coldniko @GMHikaru
The Hired Gun is building out a chess site. Come check it out themightyjoshua.com.
The Hired Gun is building out a chess site. Come check it out themightyjoshua.com.



















