Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
best sandbox for trying risky tools
#11
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
curious and caffeinated
Reply
#12
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher.
Reply
#13
A couple things I'd check first. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#14
Quote:A couple things I'd check first. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glam

What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. At this point the real bottleneck is my patience.
trying not to rebuild again
Reply
#15
I think the bottleneck is somewhere else. I get why that seems right, but on GB200 the bottleneck felt elsewhere.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)