logoalt Hacker News

porphyratoday at 5:02 PM3 repliesview on HN

> llama server where the model is, which context size to use, what to use for the K/V cache quant, that it should do MTP, tune some MTP parameters, and that's kinda it.

isn't that the hard part? You know the ballpark ideal values for these many parameters since you're a knowledgeable expert but the vast majority of people are just like "I want AI" and have no idea what all the jargon even means.


Replies

solenoid0937today at 5:06 PM

Sure, but front ends like LMStudio exist for that crowd

Otherwise, if you're a programmer setting up a local harness, it only takes like 20-30 minutes to learn what the right parameters are.

It's very model, hardware, and use case dependent which is why a one size fits all solution doesn't work

manquertoday at 5:07 PM

Why would they wish to handcraft this ? That is what agents are for ?

They could ask your current agent to a) search for this type of content online for the optimal setup for their hardware b) have the current agent/harness spin it up have it verify the config run few experiments.

Sure AI may make mistakes, or won't get the best possible config probably, but it certainly do a good enough setup, this is a task with feedback on whether the server crashed or poor performance easily measured so the agent can do a pretty good job.

show 1 reply
bmitctoday at 5:06 PM

This is exactly it. I already have broad access to Claude, Gemini, GitHub Copilot. I want to use open models on automated tasks that chew up tokens but where I don't necessarily need the best-in class models and UX.

For Claude, I setting a single config file and then download and run Claude Code CLI. Even easier for the GitHub Copilot CLI.