Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
new here, what's your stack with SGLang
#11
Interesting, I hadn't tried that. The pattern around INT4 has been pretty similar for me.
Reply
#12
Quote:Interesting, I hadn't tried that. The pattern around INT4 has been pretty similar for me.

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#13
A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#14
Tried to reproduce it just now. 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.
curious and caffeinated
Reply
#15
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)