Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JAX for inference only on dual 3090
#1
Posting this in case it saves someone else a little time.

I'm not trying to build a perfect architecture diagram. I just want a sane starting point around TensorRT-LLM and 4090.

I'm especially interested in mistakes worth avoiding.

This is mostly for local work rather than public serving.
rack in the garage • local models everywhere
Reply
#2
subscribed, curious where this lands.

I'm happy to test one more variant if you want a second data point.
serving stack tinkerer
Reply
#3
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there.
Reply
#4
Quote:My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there.

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.
context windows are not a product strategy
Reply
#5
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Reply
#6
A couple things I'd check first. On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives.
watching release notes so you don't have to
Reply
#7
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly.
learning in public
Reply
#8
Thanks, that helps. I ended up in about the same place using TensorRT-LLM. The biggest change for me was simplifying the stack instead of adding one more optimization layer. The logs were somehow calmer than I was.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#9
Appreciate the detail. The pattern around HBM constraints has been pretty similar for me.
Reply
#10
Interesting, I hadn't tried that. 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.
learning in public
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)