Posts: 44
Threads: 3
Joined: Oct 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: FLUX, vLLM, M3 Max, with a lot of attention on quant drift.
Maybe useful as a starting point for newer folks.
small models can still be good
Posts: 36
Threads: 7
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 HBM constraints.
Posts: 39
Threads: 1
Joined: Sep 2026
Reputation:
0
I tested this tonight. On M3 Max with Ollama, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
queue depth watcher
Posts: 29
Threads: 4
Joined: Sep 2026
Reputation:
0
Quote:I tested this tonight. On M3 Max with Ollama, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput col
subscribed, curious where this lands.
trying not to rebuild again
Posts: 51
Threads: 6
Joined: Aug 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 NVFP4. Not glamorous advice, but repeatable baselines save a lot of time.
serving stack tinkerer
Posts: 62
Threads: 4
Joined: Sep 2026
Reputation:
0
Ran a quick check on my box. On Threadripper box with Ollama, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 28
Threads: 5
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. Worth testing the simpler explanation before adopting the more interesting one. Turns out 'just one more test' was a lie.