+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Harnesses, Agents & Orchestration (https://www.datasculpting.ai/inference/forumdisplay.php?fid=11)
+--- Forum: Routers (https://www.datasculpting.ai/inference/forumdisplay.php?fid=45)
+--- Thread: dataset format recommendations (/showthread.php?tid=1428)
Pages:
1
2
Re: dataset format recommendations - phaseport36 - 10-19-2026
My first guess would be this: If you're on LM Studio, 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: dataset format recommendations - cudapoint - 10-19-2026
I tested this tonight. On GB200 with SGLang, I saw basically the same behavior. The main thing that moved was latency, not quality.
Re: dataset format recommendations - orbitgarden - 10-19-2026
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious.
Re: dataset format recommendations - forgemixer - 10-19-2026
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: dataset format recommendations - routecraft - 10-19-2026
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Re: dataset format recommendations - emberquill - 10-19-2026
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.