LocalLLaMA

hideshow 7 child comments

[–] cecilkorik@lemmy.ca 8 points 3 days ago (3 children)

I agree with the sentiment in general, ollama sucks and is problematic, but the obstacle that stands in the way of that is reflected pretty much right here:

llama-swap handles multi-model orchestration, loading, unloading, and hot-swapping models on demand behind a single API endpoint. Pair it with LiteLLM and you get a unified OpenAI-compatible proxy that routes across multiple backends with proper model aliasing.

The article is just vaguely asserting people can go ahead and install 3 different applications and then figure out how to configure them to talk to each other and do all the things you want it to do seamlessly, without ever even attempting to explain how to actually do that, just to get what ollama does in 1 installer.

hideshow 3 child comments

parent

[–] hendrik@palaver.p3x.de 9 points 3 days ago*

Yeah, pick your poison. And mind this article is a few months old. I'm not sure where we're at as of today, but plain llama.cpp has multi model routing built in as well. Not sure if all of those extra steps are still necessary to do.

parent

[–] chaospatterns@lemmy.world 2 points 3 days ago*

Ignoring the other comments around complexity. If anybody is considering running LiteLLM in their lab. I strongly recommend looking at GOModel instead. LiteLLM was nothing but bugs, slow page loads, and security issues for me. GOModel just worked and was simple.

parent

[–] Kissaki@programming.dev 1 point 2 days ago

That's one alternative they describe. They also mention other all-in-one alternatives. Ollama is not the only one of its kind.

parent

[–] absGeekNZ@lemmy.nz [S] 3 points 3 days ago (2 children)

Interesting; what do you suggest to run in its place?

hideshow 2 child comments

parent

[–] e0qdk@reddthat.com 5 points 3 days ago

I started with ollama then moved to llama.cpp directly and just use it through llama-server and my own custom code now. The lack of ability to use mmproj for community models (meaning things like vision processing in uncensored qwen did not work at all!) plus the fact that I had to edit a modelfile every time I want to change temperature pushed me over the edge to figure out the rough edges around llama.cpp. There have been a few bumps in the road, but it's been worth doing overall.

parent

[–] hendrik@palaver.p3x.de 5 points 3 days ago* (last edited 3 days ago)

The blog article recommends you go straight to the source and use llama.cpp and it's llama-server. And they mention a few other options as well. I did that for a while, but I'm mostly using KoboldCPP. Guess it depends on what people are trying to accomplish, but it's packed with features, fairly easy to set up and operate and does images and audio as well. (But then I don't use AI all that much, so maybe don't take advice from me.)