![]() |
|
dataset format recommendations: early impressions - Printable Version +- 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: early impressions (/showthread.php?tid=1141) Pages:
1
2
|
Re: dataset format recommendations: early impressions - batchshed - 10-18-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. Re: dataset format recommendations: early impressions - routecraft - 10-18-2026 That matches what I was seeing. The pattern around speculative decoding has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer. Re: dataset format recommendations: early impressions - cudapoint - 10-18-2026 I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. Re: dataset format recommendations: early impressions - quantghost - 10-18-2026 Can you fill in a bit more context? What model, what runtime, and roughly what context size? Re: dataset format recommendations: early impressions - thetaarch43 - 10-19-2026 A couple questions before I guess too hard. Is this local-only or are you routing anything externally? Re: dataset format recommendations: early impressions - batchember - 10-19-2026 Good point. I don't think your conclusion is far off. |