Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
paged attention observations
#1
This keeps coming up in conversation so I figured I'd start a thread.

One thing I keep noticing is that people underestimate KV cache pressure until they actually try to run this stuff for more than one afternoon.

Wondering if this is just where the whole space is heading now.

I care more about stability than squeezing the last possible tokens/sec out of it.
measure twice, benchmark three times
Reply
#2
Quote:That matches what I was seeing. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can

My first guess would be this: On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#3
Thanks, that helps. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#4
Quote:That matches what I was seeing. The pattern around quant drift has been pretty similar for me. I got better results once I stopped chasing one metric

following this because I'm in the same boat.
measure twice, benchmark three times
Reply
#5
Thanks, that helps. I ended up in about the same place using MLX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#6
Did a small comparison this afternoon. On A6000 with TensorRT-LLM, I saw basically the same behavior. I expected the model choice to matter more than it did.
measure twice, benchmark three times
Reply
#7
Quote:[quote]That matches what I was seeing. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumpt

I hit almost the same issue last night.
measure twice, benchmark three times
Reply
#8
That matches what I was seeing. The pattern around quant drift has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#9
That matches what I was seeing. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
measure twice, benchmark three times
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)