+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Security, Privacy & Safety (https://www.datasculpting.ai/inference/forumdisplay.php?fid=23)
+--- Forum: Model / Agent Security (https://www.datasculpting.ai/inference/forumdisplay.php?fid=77)
+--- Thread: sandboxing agent actions on M3 Max (/showthread.php?tid=290)
Pages:
1
2
sandboxing agent actions on M3 Max - llmpeak - 09-16-2026
Did a bit of testing and thought I'd post the result here.
After a few runs on dual 3090, I ended up with decent performance, but the setup only really made sense once I adjusted around embeddings.
Happy to post more details if anyone wants them.
Re: sandboxing agent actions on M3 Max - southpatch - 09-16-2026
Thanks, that helps. I ended up in about the same place using PyTorch. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: sandboxing agent actions on M3 Max - labline - 09-16-2026
that fixed it for me too.
Re: sandboxing agent actions on M3 Max - rocmcrate26 - 09-16-2026
Maybe, but I had the opposite result. I've seen people blame embeddings when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Re: sandboxing agent actions on M3 Max - homelabhenry - 09-16-2026
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Re: sandboxing agent actions on M3 Max - ggufvault - 09-16-2026
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Re: sandboxing agent actions on M3 Max - visionforge - 09-16-2026
Quote:My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Once you know the plain path wo
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: sandboxing agent actions on M3 Max - vectorhouse71 - 09-16-2026
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.
Re: sandboxing agent actions on M3 Max - sparrowghost - 09-16-2026
What worked for me was pretty simple. On Threadripper box, 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.
Re: sandboxing agent actions on M3 Max - cudascope - 09-17-2026
Interesting, I hadn't tried that. The pattern around NVFP4 has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.