Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
non-AI thing you built recently
#1
Did a bit of testing and thought I'd post the result here.

Short version: PyTorch behaved well for me, but only after I stopped ignoring quant drift.

Curious if anyone else landed in the same place.
curious and caffeinated
Reply
#2
I'd start with the simpler stack.
trying not to rebuild again
Reply
#3
What worked for me was pretty simple. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#4
I hit almost the same issue last night.
still benchmarking everything
Reply
#5
I'd start with the simpler stack.
Reply
#6
I don't think that's the whole story. I've seen people blame KV cache pressure when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
small models can still be good
Reply
#7
Appreciate the detail. That matches what I saw on B200.
post logs or it didn't happen
Reply
#8
Good point. The pattern around long context has been pretty similar for me.
Reply
#9
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#10
Need a little more detail here. What model, what runtime, and roughly what context size?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)