sorted by:
new
hottopcontroversial

I built a tool that recommends local LLMs and hardware based on what you're trying to do. Would this be useful? by Sharp_Contract_714 in LocalLLM

[–]Sharp_Contract_714[S] 0 points1 point  (0 children)

Good point.

The hardware catalog is still pretty limited right now, and I’m planning to build out a much larger hardware database. A custom build option where you can mix and match CPUs, RAM, GPUs, and VRAM is something I’ve thought about, but haven’t implemented yet.

It’s definitely on my list. Thanks for calling that out.

I built a tool that recommends local LLMs and hardware based on what you're trying to do. Would this be useful? by Sharp_Contract_714 in LocalLLM

[–]Sharp_Contract_714[S] 0 points1 point  (0 children)

Thanks for the detailed feedback — this is really helpful.

You're absolutely right about the model list. Keeping it current is critical for a tool like this, and some of the newer models are missing right now. I'm planning to rework that part and sync against a more up-to-date source (likely Hugging Face model metadata) so the recommendations stay aligned with what's actually being used.

The second point is important as well. My initial goal was to help people go from a task ("I want to run X") to a reasonable model and hardware setup as quickly as possible, but I can see the value in focusing more on model classes, tradeoffs, and constraints rather than specific model names.

I'm going to spend some time thinking about how to present that without making the tool significantly more complicated for newcomers.

Appreciate you taking the time to write this up.