view the rest of the comments
LocalLLaMA
Welcome to LocalLLaMA! Here we discuss running and developing machine learning models at home. Lets explore cutting edge open source neural network technology together.
Get support from the community! Ask questions, share prompts, discuss benchmarks, get hyped at the latest and greatest model releases! Enjoy talking about our awesome hobby.
As ambassadors of the self-hosting machine learning community, we strive to support each other and share our enthusiasm in a positive constructive way.
Rules:
Rule 1 - No harassment or personal character attacks of community members. I.E no namecalling, no generalizing entire groups of people that make up our community, no baseless personal insults.
Rule 2 - No comparing artificial intelligence/machine learning models to cryptocurrency. I.E no comparing the usefulness of models to that of NFTs, no comparing the resource usage required to train a model is anything close to maintaining a blockchain/ mining for crypto, no implying its just a fad/bubble that will leave people with nothing of value when it burst.
Rule 3 - No comparing artificial intelligence/machine learning to simple text prediction algorithms. I.E statements such as "llms are basically just simple text predictions like what your phone keyboard autocorrect uses, and they're still using the same algorithms since <over 10 years ago>.
Rule 4 - No implying that models are devoid of purpose or potential for enriching peoples lives.
You don't need to worry about the split in strix halo, it runs a unified memory architecture so Linux will dynamically allocate VRAM on demand up to maximum possible (which would be around 120GB I think)
I'm on an nvidia system so can't answer the rest of your questions other than to say that in my experience ollama gave me a much worse tokens per second speed compared to running the same model using llama.cpp, so if you get something slower than you expect it might be ollama caused.
Good luck with your £250 system 😉
that being said, most apps won't recognize the unified memory because because the Strix Halo is so new, so if you want accurate reporting of GPU usage, you have to set a specific amount. otherwise it will probably report 100% usage of 512M VRAM in apps like btop.
That's what I assumed it would do. Tried running an 80gb model and it barfed saying it was 'out of memory'. The LLM I consulted said it was because it needs to load the model into system RAM first then pass it to VRAM (It was set at the default 96GB RAM/32GB VRAM).
I know. Bargain, right? 🥴