Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
industry move that matters for local users
#11
Interesting, I hadn't tried that. I don't think your conclusion is far off.
watching release notes so you don't have to
Reply
#12
Tried to reproduce it just now. On GB200 with MLX, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#13
same here on my side.
Reply
#14
What exact setup are you running? What model, what runtime, and roughly what context size?
Reply
#15
Interesting, I hadn't tried that. I ended up in about the same place using LM Studio. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
trying not to rebuild again
Reply
#16
What worked for me was pretty simple. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious.
watching release notes so you don't have to
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)