Posts: 38
Threads: 9
Joined: Sep 2026
Reputation:
0
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
Posts: 38
Threads: 9
Joined: Sep 2026
Reputation:
0
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
Posts: 211
Threads: 21
Joined: Sep 2026
Reputation:
0
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
Posts: 58
Threads: 8
Joined: Sep 2026
Reputation:
0
What exact setup are you running? What model, what runtime, and roughly what context size?
trying not to rebuild again
Posts: 112
Threads: 12
Joined: Sep 2026
Reputation:
0
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
Posts: 199
Threads: 27
Joined: Sep 2026
Reputation:
0
same here on my side.
M3 Max • MLX • local-first