Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
do small edge boxes make sense
#1
I'm trying to sanity-check my setup.

My current setup is vLLM with mini PC, and I keep running into small local stacks.

Not looking for the perfect answer, mostly what worked in real use. The logs were somehow calmer than I was.
Reply
#2
Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#3
Good point. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
local image tinkerer
Reply
#4
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
Reply
#5
Quote:Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quali

worth checking the driver first.
Reply
#6
following this because I'm in the same boat.
Reply
#7
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tail latency. Once you know the plain path works, then add the faster path back in piece by piece.
trying not to rebuild again
Reply
#8
That matches what I was seeing. The pattern around reranking has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)