Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
containment for model-driven automation
#1
I figured I'd ask here before changing everything.

I'm mostly working with DeepSeek in llama.cpp on B200. The part I'm trying to understand is NVFP4.

If you've tested something similar, what did you keep and what did you stop bothering with?

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
mostly local
Reply
#2
Quote:What exact setup are you running? Are you testing this on M3 Max or something else?

Appreciate the detail. I ended up in about the same place using MLX.
Reply
#3
I'd approach it in a boring order. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time. The logs were somehow calmer than I was.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#4
Appreciate the detail. The pattern around router policy has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
context windows are not a product strategy
Reply
#5
subscribed, curious where this lands.
Reply
#6
Quote:subscribed, curious where this lands.

that fixed it for me too.
Reply
#7
Quote:
Quote:subscribed, curious where this lands.

Need a little more detail here. Are you testing this on dual 3090 or something else?

I'm happy to test one more variant if you want a second data point. I keep promising myself this is the last rebuild.
Reply
#8
What exact setup are you running? Are you testing this on M3 Max or something else?

I'm happy to test one more variant if you want a second data point.
team red, team patient
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)