![]() |
|
VRAM saving for image generation: what are you seeing? - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Evaluation & Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=16) +--- Forum: Model Comparisons (https://www.datasculpting.ai/inference/forumdisplay.php?fid=67) +--- Thread: VRAM saving for image generation: what are you seeing? (/showthread.php?tid=1388) Pages:
1
2
|
Re: VRAM saving for image generation: what are you seeing? - edgekite - 10-18-2026 Appreciate the detail. The pattern around KV cache pressure has been pretty similar for me. Re: VRAM saving for image generation: what are you seeing? - relayforge - 10-18-2026 Quote:A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt? What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt? Re: VRAM saving for image generation: what are you seeing? - cobaltlab - 10-18-2026 Quote:Appreciate the detail. The pattern around KV cache pressure has been pretty similar for me. that fixed it for me too. Re: VRAM saving for image generation: what are you seeing? - sparrowkite53 - 10-18-2026 Quote:Quote:Appreciate the detail. The pattern around KV cache pressure has been pretty similar for me. I'd start with the simpler stack. Re: VRAM saving for image generation: what are you seeing? - batchfield55 - 10-19-2026 Thanks, that helps. The pattern around token cost has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: VRAM saving for image generation: what are you seeing? - sanescope - 10-19-2026 I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. |