ollama-ui VS llama.cpp

This is great. I was thinking about putting something like this together for personal use, so - thanks for saving us the trouble!

Ollama support would be amazing, especially with the recent integration of codellama and phind-codellama. I’m sure you’re aware, but for the benefit of anyone else: there is a third party Ollama web ui[1] linked to from the ollama project homepage. It’s barebones, but does the trick.

[1]: https://github.com/ollama-ui/ollama-ui

if you can compile stuff, then looking at llama.cpp (what ollama uses) is also interesting: https://github.com/ggerganov/llama.cpp

the server is here: https://github.com/ggerganov/llama.cpp/tree/master/examples/...

And you can search for any GGUF on huggingface

Yes, Metal seems to allow a maximum of 1/2 of the RAM for one process, and 3/4 of the RAM allocated to the GPU overall. There’s a kernel hack to fix it, but that comes with the usual system integrity caveats. https://github.com/ggerganov/llama.cpp/discussions/2182

For anyone interested in exploring this, llama.cpp has an example implementation here:

https://github.com/ggerganov/llama.cpp/tree/master/examples/...

Getting started with LLMs can be intimidating. In this tutorial we will show you how to fine-tune a large language model using LoRA, facilitated by tools like llama.cpp and KitOps.

well https://github.com/ggerganov/llama.cpp/issues/6849