![]() |
|
model merge got better or just different - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Harnesses, Agents & Orchestration (https://www.datasculpting.ai/inference/forumdisplay.php?fid=11) +--- Forum: MCP / APIs / Tool Calling (https://www.datasculpting.ai/inference/forumdisplay.php?fid=46) +--- Thread: model merge got better or just different (/showthread.php?tid=728) |
model merge got better or just different - quiettoken - 10-03-2026 Thought I'd post a small recipe because a lot of threads ask similar things. Maybe useful as a starting point: TensorRT-LLM on 7900 XTX, keeping MoE serving in mind from the start. If someone wants the exact settings I can clean them up and post them. I care more about stability than squeezing the last possible tokens/sec out of it. Re: model merge got better or just different - pixelspark - 10-06-2026 Maybe, but I had the opposite result. 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: model merge got better or just different - nanopatch - 10-06-2026 I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tail latency. |