though I don't disagree with you, I'm going to argue that it's been a great learning investment in how AI and LLMs work more generally. there is also something to the comfort of keeping personal information private to you and the usefulness of most local models as most useful intelligence does not need a frontier model. I'll finish by saying that I'm taking this position mostly to protect my own self esteem knowing that I probably won't recoup my money lol.
Whole loop on one RTX 5060 Ti 16GB: Qwen plans/codes → Z-Image paints → UltraSharp for 4K → Ornith restored.
Local wallpaper factory. No cloud gen API.
Built a local digital-art wallpaper pipeline on an RTX 5060 Ti 16GB.
Desktop 1080p → desktop 4K → phone 1080p → phone 4K. One GPU. One theme: Blade Runner night, empty streets, flying cars only.
Agent that wrote it: Qwen3.8 27B UD-Q2 xhigh. Image model: Z-Image Turbo Q8.
🧵
@HenrykAbram@bojarowski@Bentyn What does the 32gb ram do? you lose all your speed if you offload anything to ram. further to that as you approach 100k context, that speed drops dramatically due to context processing.
@superalesha Dude, this is amazing. Thank you, I've been looking to understand the difference between quants beyond individual feelings on it and you delivered like crazy. Please keep doing runs like this if you can.
Benchmarked KVarN vs turbo3 the right way — same weights, same context, same MTP. Qwen3.8-27B (Q3_K_XL @ 100k, all-on-GPU): turbo3 = 30 t/s, KVarN = 10 t/s (~3×). Ornith-1.5 (Q4, CPU-offloaded experts): equal (30 t/s). The KVarN speed tax only shows when the model is fully GPU-resident. 🧵
Quality is why KVarN exists. kvarn5/kvarn4 = 5-bit K / 4-bit V vs turbo3's 3.125-bit, plus the last 1024 tokens stored exact. Anbeeld's own matrix: kvarn5/kvarn4@1024 lands within ~3% of q8_0 quality for 37% less KV memory.
@jacekdziwisz I'd be curious to understand whether there was any foresight here or not. It seems like apple is going to be in a great position to compete in the local AI space with high intelligence open weight models for years to come.
Set up a local coding stack on an RTX 5060 Ti 16GB + 32GB DDR5.
Target was simple: keep Ornith 1.5 35B-A3B loaded, use the full 262K context, and not live at 10 tok/s.
Landed at 35–40 tok/s.
Why this combo: • MoE keeps active params small enough for a 16GB card • APEX MTP is the speed bump • TurboQuant3 is what makes 262K practical on 32GB RAM • FP16 mmproj so vision doesn’t eat the quality budget