+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Security, Privacy & Safety (https://www.datasculpting.ai/inference/forumdisplay.php?fid=23)
+--- Forum: Sandboxing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=78)
+--- Thread: best sandbox for trying risky tools (/showthread.php?tid=709)
Pages:
1
2
Re: best sandbox for trying risky tools - promptfield - 10-12-2026
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Re: best sandbox for trying risky tools - sparrowkite53 - 10-12-2026
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher.
Re: best sandbox for trying risky tools - vrambandit - 10-13-2026
A couple things I'd check first. If you're on PyTorch, 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.
Re: best sandbox for trying risky tools - batchpeak - 10-13-2026
Quote:A couple things I'd check first. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glam
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. At this point the real bottleneck is my patience.
Re: best sandbox for trying risky tools - sparrowcraft - 10-13-2026
I think the bottleneck is somewhere else. I get why that seems right, but on GB200 the bottleneck felt elsewhere.