![]() |
|
comparing models without fooling yourself - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Evaluation & Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=16) +--- Forum: Benchmarks (https://www.datasculpting.ai/inference/forumdisplay.php?fid=65) +--- Thread: comparing models without fooling yourself (/showthread.php?tid=986) Pages:
1
2
|
Re: comparing models without fooling yourself - griffinloom66 - 10-19-2026 Quote:Thanks, that helps. The pattern around structured output has been pretty similar for me. I got better results once I stopped chasing one metric and ju I'd approach it in a boring order. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: comparing models without fooling yourself - cacheline - 10-19-2026 Quote:[quote]Thanks, that helps. The pattern around structured output has been pretty similar for me. I got better results once I stopped chasing one metric I think the bottleneck is somewhere else. I've seen people blame prefix caching when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup. Re: comparing models without fooling yourself - benchplease - 10-19-2026 What worked for me was pretty simple. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Re: comparing models without fooling yourself - cobaltworks25 - 10-19-2026 Quote:What worked for me was pretty simple. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did. Re: comparing models without fooling yourself - circuitworks90 - 10-19-2026 I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality. Re: comparing models without fooling yourself - deltastation - 10-19-2026 I tested this tonight. My result was mixed: first run looked bad, second run looked normal. |