Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
dataset format recommendations: early impressions
#1
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
Reply
#2
Quote:Thought I'd post a small recipe because a lot of threads ask similar things.

A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#3
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.
Reply
#4
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
Reply
#5
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
Reply
#6
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
Reply
#7
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.
Reply
#8
Quote: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 befor

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. Once you know the plain path works, then add the faster path back in piece by piece.
serving stack tinkerer
Reply
#9
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.
Reply
#10
Quote:Good point. I don't think your conclusion is far off.

Appreciate the detail. That matches what I saw on 7900 XTX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)