Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
hybrid retrieval results: early impressions
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

This isn't revolutionary, but the combination of TensorRT-LLM and mini PC felt surprisingly usable once I tuned around VRAM headroom.

Feel free to tear it apart if you see something dumb.
retrieval before vibes
Reply
#2
same here on my side.
Reply
#3
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.
curious and caffeinated
Reply
#4
What worked for me was pretty simple. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
context windows are not a product strategy
Reply
#5
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.
trying not to rebuild again
Reply
#6
following this because I'm in the same boat.
routing beats arguing over one perfect model
Reply
#7
Thanks, that helps. I don't think your conclusion is far off.
Reply
#8
that fixed it for me too.
learning in public
Reply
#9
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#10
subscribed, curious where this lands.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)