Posts: 45
Threads: 8
Joined: Sep 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Maybe useful as a starting point: vLLM on 4090, keeping MoE serving in mind from the start.
If someone wants the exact settings I can clean them up and post them.
team red, team patient
Posts: 27
Threads: 3
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there.
mostly local
Posts: 32
Threads: 1
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 26
Threads: 5
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I don't think your conclusion is far off.
Posts: 68
Threads: 10
Joined: Sep 2026
Reputation:
0
Need a little more detail here. What model, what runtime, and roughly what context size?
Posts: 43
Threads: 8
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. The logs were somehow calmer than I was.
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
Quote:A couple things I'd check first. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives.
A couple things I'd check first. On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives.
post logs or it didn't happen
Posts: 28
Threads: 5
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. The pattern around continuous batching has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.