Posts: 43
Threads: 8
Joined: Sep 2026
Reputation:
0
Did a bit of testing and thought I'd post the result here.
Short version: vLLM behaved well for me, but only after I stopped ignoring embeddings.
Nothing scientific here, just practical notes from a real setup.
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. On dual 3090 with llama.cpp, I saw basically the same behavior.
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
measure twice, benchmark three times
Posts: 57
Threads: 8
Joined: Oct 2026
Reputation:
0
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Posts: 41
Threads: 0
Joined: Oct 2026
Reputation:
0
What exact setup are you running? Is this local-only or are you routing anything externally?
Posts: 27
Threads: 3
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
mostly local
Posts: 121
Threads: 15
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
image models by night, local pipelines by day
Posts: 31
Threads: 5
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size.