Live data from Hacker News

Ollama and gguf

github.com

91–97 of 97 posts

Re: Ollama and gguf

#91

Earlier quoted context omitted.

You shouldn't use Ollama as a beginner either. It comes with crazy begginer-hostile defaults out of the box.

Hmm? I would argue against that line of argumentation. It is ridiculously easy to start out of box and working. Once the user starts moving against obvious restrictions resulting from the trade-offs in defaults, they can move on to something more custom. Woulnd't that be the definition of beginner friendly? I am biased since I effectively started with Ollama as my main local llm so take this response for what it is.…

> Which defaults you consider hostile

The infamous Ollama context limits, for one.

Re: Ollama and gguf

#92

Earlier quoted context omitted.

Hmm? I would argue against that line of argumentation. It is ridiculously easy to start out of box and working. Once the user starts moving against obvious restrictions resulting from the trade-offs in defaults, they can move on to something more custom. Woulnd't that be the definition of beginner friendly? I am biased since I effectively started with Ollama as my main local llm so take this response for what it is.…

> Which defaults you consider hostile The infamous Ollama context limits, for one.

It is infamous, but does it really stop anyone from exploring it. Granted, I am an anecdote, but flawed as it is, I would personally argue that the imposed limits are perfectly fine for someone, who is just starting. After all, those can be changed once you get your bearings.

Re: Ollama and gguf

#93

Earlier quoted context omitted.

I got to speak with some of the leads at Ollama and asked more or less this same question. The reason they abandoned llama.cpp is because it does not align with their goals. llama.cpp is designed to rapidly adopt research-level optimisations and features, but the downside is that reported speeds change all the time (sometimes faster, sometimes slower) and things break really often. You can't hope to establish contrac…

This is a good handwave-y answer for them but truth is they've always been allergic to ever mentioning llama.cpp, even when legally required, they made a political decision instead of an engineering one, and now justify it to themselves and you by handwaving about it somehow being less stable than the core of it, which they still depend on. A lot of things happened to get to the point they're getting called out aggre…

> but truth is they've always been allergic to ever mentioning llama.cpp

well, it's literally named "o"-llama, so...

Re: Ollama and gguf

#94

Earlier quoted context omitted.

This is a good handwave-y answer for them but truth is they've always been allergic to ever mentioning llama.cpp, even when legally required, they made a political decision instead of an engineering one, and now justify it to themselves and you by handwaving about it somehow being less stable than the core of it, which they still depend on. A lot of things happened to get to the point they're getting called out aggre…

> but truth is they've always been allergic to ever mentioning llama.cpp well, it's literally named "o"-llama, so...

"llama" is the name of the open-weights model released by meta for which llama.cpp (not by meta) was originally designed. llama.cpp now supports many models, not just llama. they're separate projects with separate authors.

Re: Ollama and gguf

#95

Earlier quoted context omitted.

> but truth is they've always been allergic to ever mentioning llama.cpp well, it's literally named "o"-llama, so...

"llama" is the name of the open-weights model released by meta for which llama.cpp (not by meta) was originally designed. llama.cpp now supports many models, not just llama. they're separate projects with separate authors.

ah, OK, thanks for the clarification

Re: Ollama and gguf

#96
post #44

Earlier quoted context omitted.

The Ollama distribution size is already pretty big (at least on Windows) due to all the GPU support libraries and whatnot. Having to multiple that by the number of llama.cpp versions supported would not be great.

? llamacpp> ls -l \*llama\* -rwxr-xr-x 1 root root 2505480 Aug 7 05:06 libllama.so -rwxr-xr-x 1 root root 5092024 Aug 7 05:23 llama-server That's a terrible excuse, Llama.cpp is just 7.5 megabytes. You can easily ship a couple copies of that. The current ollama for windows download is 700MB. I don't buy it. They're not willing to make an 700MB download a few megabytes bigger to ~730MB, but they are willing to support…

Sorry, I forgot to include in my comment this part:

If you include multiple version of llama, and each of those llama version depends on different GPU libraries, that could balloon the download size.

If these GPU libraries change rarely, then yes, you are correct, it might not be a problem.

Re: Ollama and gguf

#97
post #44

Earlier quoted context omitted.

? llamacpp> ls -l \*llama\* -rwxr-xr-x 1 root root 2505480 Aug 7 05:06 libllama.so -rwxr-xr-x 1 root root 5092024 Aug 7 05:23 llama-server That's a terrible excuse, Llama.cpp is just 7.5 megabytes. You can easily ship a couple copies of that. The current ollama for windows download is 700MB. I don't buy it. They're not willing to make an 700MB download a few megabytes bigger to ~730MB, but they are willing to support…

Sorry, I forgot to include in my comment this part: If you include multiple version of llama, and each of those llama version depends on different GPU libraries, that could balloon the download size. If these GPU libraries change rarely, then yes, you are correct, it might not be a problem.

Well llama.cpp requires minimum CUDA 11 from 2020, or if you need CUDA C++17 support, then CUDA 12 from 2022.

It'll compile fine against latest CUDA 12.8 or 12.9 etc, but there's zero need to pack whatever the latest CUDA version is.

Post reply on HN