Posts: 40
Threads: 8
Joined: Sep 2026
Reputation:
0
Has anyone else run into this?
My current setup is TensorRT-LLM with Threadripper box, and I keep running into VRAM headroom.
Not looking for the perfect answer, mostly what worked in real use.
I expected the biggest difference to come from the model, but the stack around it mattered at least as much.
Posts: 52
Threads: 6
Joined: Sep 2026
Reputation:
0
Good point. The pattern around structured output has been pretty similar for me.
Posts: 38
Threads: 5
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on 5090.
Posts: 28
Threads: 1
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I ended up in about the same place using TensorRT-LLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
If you post your exact settings, people here can probably narrow it down pretty fast.
mostly local
Posts: 31
Threads: 3
Joined: Sep 2026
Reputation:
0
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
team red, team patient
Posts: 32
Threads: 4
Joined: Aug 2026
Reputation:
0
What worked for me was pretty simple. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
curious and caffeinated
Posts: 45
Threads: 4
Joined: Aug 2026
Reputation:
0
My first guess would be this: On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 17
Threads: 4
Joined: Sep 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
curious and caffeinated