Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MLX model loading quirks
#1
Maybe I'm missing something obvious.

My current setup is TensorRT-LLM with B200, and I keep running into speculative decoding.

If you've tested something similar, what did you keep and what did you stop bothering with?

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Reply
#2
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#3
subscribed, curious where this lands.
Reply
#4
A couple things I'd check first. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Turns out 'just one more test' was a lie.
M3 Max • MLX • local-first
Reply
#5
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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#6
Can you fill in a bit more context? Are you testing this on B200 or something else?
trying not to rebuild again
Reply
#7
That matches what I was seeing. I ended up in about the same place using vLLM.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)