1. The results of this tool are not good. It’s recommending outdated models like Qwen2.5 series and missing good new models. 2. This could have been a single web page that runs in your browser and lets you enter hardware specs, like all of the other tools like this. It is not a good idea to install and run unknown projects like this on your computer in this age. 3. The project is very obviously vibecoded, down to the…
There is apparently a marketing.md file that was deleted 25min ago with the strategy to post on HN. https://github.com/Andyyyy64/whichllm/commit/2cefaea1cc5d2de... I think your hunch is very much spot on. It doesn’t look trustworthy at all.
Show HN: Find the best local LLM for your hardware, ranked by benchmarks
71–80 of 80 posts
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#72This is very helpful too: https://www.canirun.ai/
Love that it defaults to the GPU being "NVIDIA GeForce 8800 GTX", a GPU released in 2006 with ~700MB of VRAM... The estimates seems far off as well, took https://www.canirun.ai/model/gpt-oss-120b as an example, with a RTX Pro 6000 and every single number is off, and notably misses estimation for the most important quant for GPT-OSS, the MXFP4 variant.
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#731. The results of this tool are not good. It’s recommending outdated models like Qwen2.5 series and missing good new models. 2. This could have been a single web page that runs in your browser and lets you enter hardware specs, like all of the other tools like this. It is not a good idea to install and run unknown projects like this on your computer in this age. 3. The project is very obviously vibecoded, down to the…
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#74I also have a script to find the best LLM for your hardware. Here: echo "Qwen3.6-27B"
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#75The plan command is clever. How do you handle the VRAM estimation for models with sliding window attention vs full context? Something like Mistral at 32k context uses way less KV cache than Llama at the same context length, but from the README it looks like the estimation is based on a fixed context size. Does it account for that?
Good catch that's a real gap. The KV estimate is GQA/MQA-aware (per-model head config) but currently assumes dense full-context attention; it does not model sliding-window / chunked attention, so for SWA models like Mistral or Gemma at long context it over-estimates KV. The error is conservative — it tells you a model needs more than it does, not less, so it won't push you into an OOM — but it's still wrong. I'll ope…
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#76This is very helpful too: https://www.canirun.ai/
Yes, I really like this site too, but it's a bit outdated. "39d ago" in AI time is like 1 year outdated info.
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#77Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#78This is very helpful too: https://www.canirun.ai/
Re: Show HN: Find the best local LLM for your hardware, ranked by benchmarks
#79This is very helpful too: https://www.canirun.ai/
Every browser gives me a different result, I guess I can't blame the site for that. But it should perhaps mention which browser would be the most accurate.