08-28-2026, 07:38 AM
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there.
|
KV cache compression worth it: worth it?
|
|
08-28-2026, 07:38 AM
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there.
08-28-2026, 04:22 PM
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
08-30-2026, 04:23 AM
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. Once you know the plain path works, then add the faster path back in piece by piece.
08-31-2026, 04:52 PM
Appreciate the detail. I ended up in about the same place using SGLang. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
08-31-2026, 05:57 PM
Thanks, that helps. The pattern around consumer GPUs has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
09-03-2026, 05:59 PM
Quote:Thanks, that helps. The pattern around consumer GPUs has been pretty similar for me. The biggest change for me was simplifying the stack instead of ad Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did. If you post your exact settings, people here can probably narrow it down pretty fast. |
|
« Next Oldest | Next Newest »
|