Can I run AI locally?
TL;DR Highlight
A browser tool that detects your GPU specs via WebGPU and recommends which LLM models you can actually run locally on your hardware.
Who Should Read
Developers and enthusiasts who want to run LLMs locally but aren't sure which models will fit their GPU/VRAM, and builders creating tools for the local AI ecosystem.
Core Mechanics
- The tool runs entirely in the browser — it uses the WebGPU API to query GPU information (model, VRAM, compute capabilities) without any server-side processing.
- Based on the detected specs, it recommends specific quantized model variants (e.g., 'Llama 3.1 8B Q4_K_M fits in your 8GB VRAM') from Hugging Face.
- It accounts for quantization levels (Q4, Q5, Q8, etc.) and model sizes to calculate what actually fits in available VRAM with headroom for the KV cache.
- The tool also distinguishes between compute-bottlenecked and memory-bottlenecked inference, helping users understand what performance to expect.
- This solves a real friction point: many people download a model that then OOM-crashes, wasting time. Having a browser-based hardware checker reduces this trial-and-error.
Evidence
- The tool was shared with source code, demonstrating the WebGPU hardware detection approach.
- HN commenters with diverse hardware confirmed the detection accuracy — it correctly identified VRAM and compute tier across NVIDIA, AMD, and Apple Silicon.
- Some noted that WebGPU doesn't expose all the detail needed (e.g., actual available VRAM after OS/other app usage), so recommendations are conservative estimates.
- Feature requests included integration with llama.cpp presets and recommendations for CPU-only inference on systems without a discrete GPU.
How to Apply
- Before downloading any local LLM model, use a tool like this to confirm your VRAM headroom — remember to account for OS VRAM usage (typically 1-2GB on most systems).
- When selecting quantization level: Q4_K_M is a good default balance of quality and size; go Q5 or Q8 only if you have sufficient VRAM to spare.
- For developers building local AI tools: providing hardware-aware model recommendations reduces friction for new users — consider integrating a similar WebGPU detection step in your onboarding.
- The WebGPU API's hardware detection capabilities (without requiring native code) is worth knowing about for browser-based developer tooling.
Terminology
Related Papers
Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k
동일한 모델과 작업 환경에서 Claude Code와 OpenCode의 실제 토큰 사용량을 API 레벨에서 측정한 결과, Claude Code가 시스템 프롬프트 오버헤드만으로 OpenCode 대비 4.7배 더 많은 토큰을 소비한다는 것을 확인했다.
Mesh LLM: distributed AI computing on iroh
사무실, 집, 클라우드에 흩어진 GPU들을 하나의 OpenAI 호환 API로 묶어주는 분산 LLM 실행 시스템으로, 비싼 API 비용 없이 큰 모델을 직접 운영할 수 있다.
Show HN: Frugon – Find which LLM calls a cheaper model could handle (local, MIT)
내 LLM API 비용이 어디서 새는지 로컬에서 분석해주는 오픈소스 CLI 도구로, 비싼 모델 대신 저렴한 모델로 전환 가능한 호출을 골라낸다.
Jamesob's guide to running SOTA LLMs locally
2천 달러짜리 RTX 3090 한 장부터 4만 달러짜리 RTX PRO 6000 4장 셋업까지, 로컬에서 최신 LLM을 직접 돌리는 방법을 하드웨어 선택·구성·실행 설정까지 통째로 정리한 실전 가이드다.
Faster embeddings: how we rebuilt the ONNX path in Manticore
Manticore Search가 기존 SentenceTransformers/Candle 백엔드를 ONNX Runtime으로 교체해 텍스트 임베딩 생성 속도를 평균 14배 향상시켰다. 별도 모델 서비스 없이 DB 내부에서 직접 임베딩을 처리하는 구조에서 INSERT 속도가 곧 임베딩 속도이기 때문에 이 개선은 실질적인 ingest 처리량 향상으로 직결된다.
Asymmetric Quantization: Near-Lossless Retrieval with 97% Storage Reduction
멀티벡터 검색 모델의 문서 벡터를 1비트 이진값으로 압축하고 쿼리 벡터만 int8로 유지하는 비대칭 양자화 기법으로, 스토리지를 97% 줄이면서 검색 품질 손실을 0.61점(NDCG@10 기준)에 그치게 만든 실제 프로덕션 적용 사례다.