![]() |
|
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=754) |
model merge got better or just different - rasterbench - 10-05-2026 Posting this in case it saves someone else a little time. I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about KV cache pressure. Simple and boring is a valid answer. Re: model merge got better or just different - thetafield - 10-05-2026 Maybe, but I had the opposite result. I get why that seems right, but on 5090 the bottleneck felt elsewhere. 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 - benchplease - 10-05-2026 A couple things I'd check first. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. |