Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
consumer accelerators worth watching
#1
Curious what people here are seeing.

My current setup is TensorRT-LLM with 5090, and I keep running into KV cache pressure.

Would appreciate practical advice rather than theory.
trying not to rebuild again
Reply
#2
Quote:Curious what people here are seeing.

Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.

I'm happy to test one more variant if you want a second data point.
Reply
#3
Quote:
Quote:Curious what people here are seeing.

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy.
Reply
#4
Thanks, that helps. The pattern around embeddings has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#5
Quote:Thanks, that helps. The pattern around embeddings has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption ca

worth checking the driver first.
Reply
#6
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
mostly local
Reply
#7
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there.
mostly local
Reply
#8
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
Reply
#9
A couple questions before I guess too hard. Are you testing this on Threadripper box or something else?
Reply
#10
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)