RamaLama
11–20 of 54 posts
Re: RamaLama
#12Re: RamaLama
#13The killer features of Ollama for me right now are the nice library of quantized models and the ability to automatically start and stop serving models in response to incoming requests and timeouts. The first send to be solved by reusing the Ollama models, but I can't see if the service is possible from my cursory look.
Re: RamaLama
#14Great, finally an alternative to ollama's convenience.
Hopefully both will be easy for users to play around with, but RamaLama should be easier to get your PR merged as a developer and swap out different registries. Vendor lock-in is rarely a good thing in the world of open source.
Re: RamaLama
#15This is the point of it: https://github.com/ggerganov/llama.cpp/pull/11016#issuecomme...
Re: RamaLama
#16So it's a replacement for Ollama? The killer features of Ollama for me right now are the nice library of quantized models and the ability to automatically start and stop serving models in response to incoming requests and timeouts. The first send to be solved by reusing the Ollama models, but I can't see if the service is possible from my cursory look.
Re: RamaLama
#17Is this useful? Can someone help me see the value add here?
Re: RamaLama
#18This looks great! While we're at it, is there already some kind of standardized local storage location/scheme for LLM models? If not, this project could potentially be a great place to set an example that others can follow, if they want. I've been playing with different runtimes (Ollama, vLLM) the last days, and I really would have appreciated better interoperability in terms of shared model storage, instead of every…
Re: RamaLama
#19This is the point of it: https://github.com/ggerganov/llama.cpp/pull/11016#issuecomme...
I'm glad there is a more open source alternative to Ollama now.