Project ideas from Hacker News discussions.

Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware

📝 Discussion Summary (Click to expand)

Theme 1 – Harness & benchmark transparency
Users stressed that the benchmark’s usefulness depends on revealing the inference harness (libraries, versions, driver details) because the harness itself can dominate latency.
- “Model list is a bit limited, and whole harness affects the speed, so the libs used in harness and their versions might be useful to show for each individual model setup.” – bozdemir
- “I’ll look into adding harnesses. The benchmark sources usually don’t contain harness so the problem is limited data.” – albinstman
- “The only bottleneck a harness attachs is pre‑context fill and whatever tooling is installed.” – cyanydeez

Theme 2 – Hardware limits & viable model choices
Commenters debated what older or mid‑range GPUs can realistically run, emphasizing VRAM constraints, the trade‑off between dense and Mixture‑of‑Experts (MoE) models, and the ability to squeeze performance from older cards.
- “I setup llm endpoints on corporate level … on H200 gpus … even on different versions of nvidia drivers … very limited VRAM like 24gb on a 4090 …” – bozdemir
- “Shame they are not including old crap like my RX580 … 8GB vram from 2017 … 20 tps generation is okay …” – hbogert
- “On a 3080 10GB and 32GB of RAM I can run the qwen‑next coder model … 40‑50 Token/s with 65k context.” – PaulKeeble
- “MOE based models get a lot more out of the hardware than a dense model … they behave a lot more like their peak size than the active parameter size.” – PaulKeeble

Theme 3 – Context length & KV‑cache quantization for agentic workloads
Several participants highlighted that agent‑style coding needs large context windows and efficient KV‑cache handling; they discussed required context sizes, quantization tricks, and the impact on throughput.
- “I’m far less concerned about output token speed and way more about the ability to parallelize prefill – for agentic coding that’s pretty much way more important than output speed.” – friendly_chap
- “Ideally you want to find something that allows a context window for at least 65k for agent work. Over 100k is better but 32k is about the bare minimum …” – PaulKeeble
- “I would go ahead and give it at least 64k … I run the kv cache at q8 for keys and q4 for values …” – trucks-refinish
- “After around 100k context it goes down to 9 tk/s but that is to be expected.” – lopotubez


🚀 Project Ideas

Generating project ideas…

Gathering the best ideas from the HN discussion…

Read Later