Posts: 38
Threads: 6
Joined: Sep 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
This isn't revolutionary, but the combination of TensorRT-LLM and mini PC felt surprisingly usable once I tuned around VRAM headroom.
Feel free to tear it apart if you see something dumb.
retrieval before vibes
Posts: 41
Threads: 7
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.
curious and caffeinated
Posts: 112
Threads: 12
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. If you're on vLLM, 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.
context windows are not a product strategy
Posts: 40
Threads: 4
Joined: Sep 2026
Reputation:
0
Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
trying not to rebuild again
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
following this because I'm in the same boat.
routing beats arguing over one perfect model
Posts: 31
Threads: 2
Joined: Oct 2026
Reputation:
0
Thanks, that helps. I don't think your conclusion is far off.
Posts: 74
Threads: 9
Joined: Sep 2026
Reputation:
0
that fixed it for me too.
learning in public
Posts: 30
Threads: 3
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 47
Threads: 6
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.