Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
desktop apps around local AI for Phi
#1
Spent some time on this today and wanted to compare notes.

I've gone back and forth between PyTorch and SGLang for Mistral. The interesting difference for me has been INT4.

Interested in tradeoffs more than fan loyalty.
Reply
#2
Thanks, that helps. The pattern around batch size 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.
7900 XTX / ROCm / somehow still optimistic
Reply
#3
that fixed it for me too.
Reply
#4
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
M3 Max • MLX • local-first
Reply
#5
My first guess would be this: If you're on PyTorch, 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.
learning in public
Reply
#6
I think the bottleneck is somewhere else. I've seen people blame prefix caching when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Reply
#7
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
Reply
#8
I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
M3 Max • MLX • local-first
Reply
#9
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
learning in public
Reply
#10
worth checking the driver first.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)