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.
view the rest of the comments
I ordered a Beelink GTR9 Pro which should hopefully arrive next month.
Really excited to play around with it, the 24GB in my 7900 XTX just don't cut it for local LLMs.
There are a lot of benchmarks for the 395 processor here: https://kyuz0.github.io/amd-strix-halo-toolboxes/
They are leaving a lot of performance (and VRAM) on the table by doing this on Windows.
I just got the FW Desktop with the 128GB 395 yesterday
Let me know if you have specific models you want me to run/benchmark.
I found most of the reviews inadequate, just running models with a 4K context. I use 64-128k.
Qwen Coder and GPT OSS 120b both run very well on the 395, I get respectable token rates with medium/long context.
Dense models can be a little slow (e.g. Gemma no quant). Prompt processing is a little slow, but not problematic.
It’s impressive how quickly I can load 60gb models into vram.
Good to hear that people are starting to get their hands on them, still have to wait ~2 weeks for mine.
Besides the benchmarks already listed on kyuz0's Github, the things that are interesting to me:
I can't run GLM 4.5 on those quants, I've been unable to get beyond 96gb vram (I know you can get 112, but I'm still a linux noob)
GPT OSS 120b (60gb) loads into clear memory in 37-45s (tested 3 times), but I think it can take up to 60s if there are other models in memory. I'm not sure what's going on there, it should take ~10s to read the model from disk, but I do get a lock error in lmstudio and an alloc failure.
I don't know how to measure idle power with a model in memory (linux noob), but it's been on my desk all day with either GPT120b or Qwen Code and has been pretty quiet (just PSU fan running off and on). With Framework the fan seems to start at aroudn 55C, the system idles with a model in memory at 45-50C.
I'll try and figure out comfyui or a nice way to run image models then get back to you. They're not really something I need/use, so I'm starting from zero on how to run them.
There's some info on how to set the kernel arguments to get full access to the 128GB as VRAM: https://github.com/kyuz0/amd-strix-halo-toolboxes?tab=readme-ov-file#6-host-configuration
There's also containers for llama.cpp and ComfyUI which have everything setup for you in that repo.
I’ll give those a run tomorrow or late tonight
I've got memory setup to use the full 128gb, downloading the IQ2_XXS GLM 4.5, and I'm also downloading the strix-halo quen image/video containers.
It's going to be a couple hours, so I'll check in tomorrow morning and update you
Edit: the qwen image toolbox is not working at all, literally zero iteration speed and none of my memory is being allocated. It seems to think I have 512MB of vram instead of the shared 128GB, this is probably a bug.
I think that is normal, it shows 512MB in his video as well.
Not sure what's going on with the zero iterations though.
Was unable to get GLM 4.5 UD in that quant through LM studio, I'll try just llama.cpp instead
edit: Runs fine in llama.cpp, 5.1-5.6 tok/s on CPU, but I can't seem to fit the whole memory on GPU. Still experimenting.
12k context seems like the largest I can get (uses 118GB). You can probably push it further without a GUI, but on a desktop environment gnome daemon starts killing processes.
Prompt processing at 12.3t/s, inference at 10.7-11.1 t/s.
I would say this verges on not-usable between the speed and context window. After the thinking tokens are through you've burned a lot of your usable context.
edit: implementing conway's game of life in numpy worked, used 3k/12k context, and took 7minutes.
Is that still on CPU or did you get it working on GPU?
I have seen a few people recommending GLM 4.5 at lower quants primarily for more intricate writing, might be worth the lower speed and context size for shorter texts.
Thanks for testing!
That was GPU, CPU was 5.
I’ve also tested the image processing more, a 512x512 takes about a minute, 1400x900 takes about 7-10, and image to image takes about 10 minutes
Most of the time is spent on the encoder decoder layers for image to image, and decoding is what shapes the slowest with image size
Edit: image Gen works through comfyui, but is slow. Exact same experience as the video, works as he says. Not rendering text literally halves the compute time, but Qwen Image works.
So I had neglected to download the models. Chalk that up to trying to do this after coming home from the bar.
Qwen image is not working in that toolbox container.
First attempt had bad memory access when trying to merge the model and LoRA, second attempt it kept trying to use CUDA so failed to generate, third attempt it reached 100% of denoising generation but started running into strong GPU lag on the rest of the desktop environment and never produced the image.
Fourth attempt failed to merge LoRA again due to HIP memory errors -- this is after a fresh reboot, so no resource contention.
Rebooted qwen, fifth attempt it does merge LoRA and start generation, but never actually finishes an iteration. For some reason this time it appears to be trying to run on 4 CPUs. This run again in the logs said it was trying CUDA, so... I suspect it's the same failure.
It looks to me like a torch configuration issue.
___Huzzah! Qwen Image! Runtime 547s
Seems pretty good for fp16, might be quite a bit faster with an fp8 workflow.
Yeah, I’ve discovered if you lower resolution and steps to ~4 you can prototype a prompt on blurry images.
Once you’ve got something with a good layout 40 steps works better
I’m a bit disappointed in Qwen image’s prompt processing, it’s good, but it does not have good knowledge and will swap people out if you ask for real people.