this post was submitted on 15 Aug 2025
17 points (100.0% liked)

LocalLLaMA

3617 readers
37 users here now

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.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] panda_abyss@lemmy.ca 2 points 3 days ago* (last edited 3 days ago) (1 children)

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.

llama-cli --ngl 93 --context 12288 --no-mmap -t 16

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.

[–] domi@lemmy.secnd.me 1 points 1 day ago (1 children)

Prompt processing at 12.3t/s, inference at 10.7-11.1 t/s.

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!

[–] panda_abyss@lemmy.ca 2 points 1 day ago

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