best sandbox for trying risky tools

[deltagrid]

Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on dual 3090, or squeeze more out of the stack and deal with the complexity.

What would you pick if you had to live with it for a few months?

This is mostly for local work rather than public serving.

[deepseeked]

Can you fill in a bit more context? Are you testing this on GB200 or something else?

[vramridge]

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at NVFP4.

[dockember]

Can you fill in a bit more context? Is this local-only or are you routing anything externally?

[circuitworks90]

What worked for me was pretty simple. On 4090, 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.

[macroforge]

What worked for me was pretty simple. On 4090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lo

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.

[batchcraft]

A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?

[cacheline]

I'd approach it in a boring order. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.

[fastquill74]

My first guess would be this: 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.

I'm happy to test one more variant if you want a second data point.