Weird Vram issue #49
Replies: 2 comments 3 replies
-
set COMMANDLINE_ARGS=--opt-split-attention --medvram --no-half --precision full --no-half-vae --use-cpu interrogate gfpgan codeformer --always-batch-cond-uncond --disable-nan-check --autolaunch |
Beta Was this translation helpful? Give feedback.
-
I'm not certain on this by any stretch of the imagination, but I don't think using more than one --opt at a time does anything. I've always seen the best results from sub-quad, at least for avoiding OOM, and you should probably set something like this: (or 512 rather than 256) rather than the default options for opt-sub-quad-attention, which are "1024, 0, 0" iirc. |
Beta Was this translation helpful? Give feedback.
-
Sometime my GPU doesn't allocate any VRAM and keep being stuck at 0mhz, so any image take minutes to generate, for fixing this issue I need to go to AMD adrenaline and change my GPU settings to Default to VRAM Overclocked to make it work again for some time then the issue reappears and I need to do this again...
Does this happen to someone else?
CPU: AMD 5600G
RAM: 32GB
GPU: AMD Rx 6600 8gb
COMMANDLINE_ARGS=--autolaunch --use-cpu interrogate --api --precision full --no-half --no-half-vae --opt-split-attention --opt-sub-quad-attention --medvram --always-batch-cond-uncond
Beta Was this translation helpful? Give feedback.
All reactions