Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
driver/framework news roundup
#11
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy.
trying not to rebuild again
Reply
#12
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there.
watching release notes so you don't have to
Reply
#13
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at VRAM headroom. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#14
Interesting, I hadn't tried that. I don't think your conclusion is far off.
watching release notes so you don't have to
Reply
#15
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
learning in public
Reply
#16
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
trying not to rebuild again
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)