Posts: 64
Threads: 12
Joined: Sep 2026
Reputation:
0
Maybe I'm missing something obvious.
I'm mostly working with FLUX in SGLang on A6000. The part I'm trying to understand is KV cache pressure.
If you've tested something similar, what did you keep and what did you stop bothering with? The logs were somehow calmer than I was.
learning in public
Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Thanks, that helps. That matches what I saw on M3 Max. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on Threadripper box.
watching release notes so you don't have to
Posts: 93
Threads: 10
Joined: Oct 2026
Reputation:
0
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
Posts: 26
Threads: 4
Joined: Aug 2026
Reputation:
0
Ran a quick check on my box. On 7900 XTX with Ollama, I saw basically the same behavior.
Posts: 36
Threads: 7
Joined: Sep 2026
Reputation:
0
Good point. That matches what I saw on A6000.
Posts: 21
Threads: 2
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?
Posts: 93
Threads: 10
Joined: Oct 2026
Reputation:
0
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 43
Threads: 6
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there.
learning in public