this post was submitted on 17 Jun 2026
261 points (97.5% liked)

Technology

85542 readers
3474 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


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

Why would a developer likely have a high end GPU? Writing code doesn’t use a GPU.

[–] VonReposti@feddit.dk 1 points 2 days ago (2 children)

There is a significant overlap between developers and gamers.

[–] GoatSynagogue@lemmy.world 6 points 2 days ago

Most developers use their work provided machines, which aren’t gaming machines with giant GPUs because again, GPUs don’t help development at all.

[–] NotMyOldRedditName@lemmy.world 2 points 2 days ago* (last edited 2 days ago) (1 children)

Also developers often want more ram, and if youre on the mac side, the M series ram works as video ram for loading and running models, so there's a good chance you can already run something better than is typical of others, and apple is focusing on this by adding more NPUs and increasing memory bandwidth. They arent good at training, but can do inference.

[–] partofthevoice@lemmy.zip 1 points 2 days ago (2 children)

I’m on a MacBook with M2, 32GB ram. Literally just tried:

  • gemma4:12b - very slow, unworkable
  • qwen3:8b - very slow, unworkable
  • qwen2.5-coder:7b - slow but workable. Doesn’t use tools properly in OpenCode.

Well, I guess I’ll try again next year.

For context: my home pc is running gemma4:31b just fine. It’s also a beefy ass desktop, though.

[–] fluxx@mander.xyz 2 points 1 day ago (1 children)

Are you running an mlx model? If not, try that. My m4 macbook runs qwen3.6-35b-a3b lightning fast. Has its issues, but fast nonetheless.

[–] NotMyOldRedditName@lemmy.world 1 points 1 day ago (1 children)

What kind of context length can you get with that, and how much ram?

[–] fluxx@mander.xyz 1 points 1 day ago (1 children)

I have a model with 64GB of ram. I've limited context to 16k, in an effort to make it more stable, but tbh - it is rather unreliable no matter what I do. With my setup - mlx_lm and webui, it frequently collapses or loops, no matter the settings. I have done a lot of debugging and have concluded it is probably inherent model behavior.

[–] NotMyOldRedditName@lemmy.world 2 points 19 hours ago* (last edited 19 hours ago)

That's lame about the looping, but ya I don't think that's a mlx issue, I've had it on my desktop with my nvidia card as well. I also tried fussing with configurations, and I was never sure if it was the models or my settings. I was mainly toying around with LLama based models.

[–] NotMyOldRedditName@lemmy.world 3 points 2 days ago* (last edited 2 days ago)

You might be doing something wrong, models that size shouldn't be that slow if properly configured on a 32gb m2

You need a metal optimized client and model, not the same models you'd run on your desktop machine.