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

This isn't revolutionary, but the combination of LM Studio and Threadripper box felt surprisingly usable once I tuned around VRAM headroom.

Feel free to tear it apart if you see something dumb.

This is mostly for local work rather than public serving.
Reply
#2
What worked for me was pretty simple. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#3
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. Once you know the plain path works, then add the faster path back in piece by piece.
rack in the garage • local models everywhere
Reply
#4
that fixed it for me too.
Reply
#5
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.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#6
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.

I'm happy to test one more variant if you want a second data point.
Reply
#7
Tried to reproduce it just now. On mini PC with vLLM, I saw basically the same behavior.
small models can still be good
Reply
#8
Appreciate the detail. The pattern around NVFP4 has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#9
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
team red, team patient
Reply
#10
I'd approach it in a boring order. On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)