Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
recipes for a good local stack
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like NVFP4 decides everything downstream.

Wondering if this is just where the whole space is heading now.
curious and caffeinated
Reply
#2
Quote:This keeps coming up in conversation so I figured I'd start a thread.

Appreciate the detail. That matches what I saw on 4090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#3
Quote:
Quote:This keeps coming up in conversation so I figured I'd start a thread.

Ran a quick check on my box. On A6000 with SGLang, I saw basically the same behavior. The main thing that moved was latency, not quality.
Reply
#4
Quote:
Quote:
Quote:This keeps coming up in conversation so I figured I'd start a thread.

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#5
Good point. That matches what I saw on mini PC. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
curious and caffeinated
Reply
#6
Quote:Good point. That matches what I saw on mini PC. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look

Good point. I ended up in about the same place using llama.cpp. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#7
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
What exact setup are you running? What model, what runtime, and roughly what context size?
trying not to rebuild again
Reply
#9
Quote:What exact setup are you running? What model, what runtime, and roughly what context size?

I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
context windows are not a product strategy
Reply
#10
same here on my side.
M3 Max • MLX • local-first
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)