Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Blackwell deployment chatter for FLUX
#1
Curious what people here are seeing.

I'm mostly working with Qwen in LM Studio on 4090. The part I'm trying to understand is prefix caching.

If you've tested something similar, what did you keep and what did you stop bothering with?
Reply
#2
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#3
Good point. The pattern around MoE serving has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Mostly CUDA, sometimes wrong, usually measured
Reply
#4
Quote:Good point. The pattern around MoE serving has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make

I'd start with the simpler stack.
learning in public
Reply
#5
Good point. The pattern around batch size has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#6
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
Reply
#7
Quote:Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.

I don't think that's the whole story. I've seen people blame tokens/sec when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#8
I tested this tonight. On Threadripper box with TensorRT-LLM, I saw basically the same behavior. The main thing that moved was latency, not quality.

I'm happy to test one more variant if you want a second data point.
Reply
#9
Not sure I agree there. I've seen people blame consumer GPUs when the real issue was much more mundane.
Reply
#10
worth checking the driver first.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)