Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
sandboxing agent actions: worth it?
#1
I'm trying to sanity-check my setup.

My current setup is PyTorch with 7900 XTX, and I keep running into consumer GPUs.

Would appreciate practical advice rather than theory.
Reply
#2
Appreciate the detail. I ended up in about the same place using LM Studio. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
local image tinkerer
Reply
#3
Thanks, that helps. The pattern around HBM constraints has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer. I keep promising myself this is the last rebuild.
Reply
#4
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.
Reply
#5
Quote:I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.

I'd approach it in a boring order. On M3 Max, 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.
Mostly CUDA, sometimes wrong, usually measured
Reply
#6
Quote:
Quote:I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.

Good point. I don't think your conclusion is far off.
trying not to rebuild again
Reply
#7
Quote:
Quote:[quote]I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.
[/qu

My first guess would be this: If you're on SGLang, 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.
Reply
#8
Need a little more detail here. What model, what runtime, and roughly what context size?

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#9
Interesting, I hadn't tried that. That matches what I saw on GB200.
trying not to rebuild again
Reply
#10
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)