+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Optimization & Performance (https://www.datasculpting.ai/inference/forumdisplay.php?fid=10)
+--- Forum: Benchmarks (https://www.datasculpting.ai/inference/forumdisplay.php?fid=43)
+--- Thread: domain tune without wrecking base behavior on B200 (/showthread.php?tid=807)
Pages:
1
2
domain tune without wrecking base behavior on B200 - sparrowworks88 - 10-06-2026
Posting this in case it saves someone else a little time.
I'm not trying to build a perfect architecture diagram. I just want a sane starting point around SGLang and 5090.
Would rather learn from your scars than collect my own all at once.
Re: domain tune without wrecking base behavior on B200 - benchplease - 10-06-2026
worth checking the driver first.
Re: domain tune without wrecking base behavior on B200 - cudascope - 10-06-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Re: domain tune without wrecking base behavior on B200 - batchpeak - 10-08-2026
that fixed it for me too.
Re: domain tune without wrecking base behavior on B200 - northgrid33 - 10-08-2026
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there.
Re: domain tune without wrecking base behavior on B200 - batchsize - 10-11-2026
I don't think that's the whole story. I've seen people blame HBM constraints 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.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Re: domain tune without wrecking base behavior on B200 - vrampilot - 10-11-2026
What worked for me was pretty simple. If you're on LM Studio, 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. I keep promising myself this is the last rebuild.
Re: domain tune without wrecking base behavior on B200 - cudascope - 10-13-2026
A couple questions before I guess too hard. Are you testing this on Threadripper box or something else?
Re: domain tune without wrecking base behavior on B200 - batchsize - 10-13-2026
A couple things I'd check first. If you're on Ollama, 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.
I'm happy to test one more variant if you want a second data point.
Re: domain tune without wrecking base behavior on B200 - deltastation - 10-13-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there.