4 ms·

Thanks! Can't wait to get a minute to check this out. Promising 2x performance over pytorch+xformers sounds too good to be true for the same card. As someone w

Thanks! Can't wait to get a minute to check this out. Promising 2x performance over pytorch+xformers sounds too good to be true for the same card. As someone with a lowly 10gb card sdxl is beyond my reach with a1111 it seems. It functions well enough in comfyui but I can't make anything but garbage with it in automatic. So I'm happy to see 1.5 gets a big boost, I know there's a million of us out there who can't quite squeeze SDXL out so the maturing of the "legacy" versions is a positive note to see.

thot_experiment 3y ago
I haven't been paying attention for a few months, is there a lot of development happening around SDXL or are people still mostly focused on 1.5? My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data, is that bearing out?
- GaggiX 3y ago
  >My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data Where do you read that SDXL has worse training data? They didn't disclose what the model was trained on like the previous models.
- Veraticus 3y ago
  Most people (and models) still use 1.5 because of hardware and performance issues with SDXL.
- dragonwriter 3y ago
  > I haven't been paying attention for a few months, is there a lot of development happening around SDXL or are people still mostly focused on 1.5? There's been a lot happening on SDXL, yes. > My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data, is that bearing out? What worse training data?
  - thot_experiment 3y ago
    > There's been a lot happening on SDXL, yes. Nice! Care to share any projects/advancements/gens you've found particularly compelling if you have anything handy? > What worse training data? I don't know this, but I think it's a pretty safe assumption given the state of 2.0/the political climate around this stuff, along with the comparative lower diversity of gens I've seen come out of SDXL. I haven't seen anything to the contrary but I'd love to be wrong.
iLoveOncall 3y ago
I've used SDXL with a 3080 (10GB) mostly without issues. You have to give some command line parameters when launching it to reduce memory use. > --medvram-sdxl --no-half-vae
- Filligree 3y ago
  "--no-half-vae" doesn't reduce memory usage, it forces A1111 to use 32-bit floats for the VAE decoding.
  - dragonwriter 3y ago
    --no-half-vae, IIRC, is required for the stock sdxl vae model because otherwise it frequently produces errors. I believe there’s a half-precision fixed VAE floating around and baked into many SDXL-derived checkpoints that avoids this problem.
DrSiemer 3y ago
Runs just fine on my 8GB card. You probably did not swap the VAE. Without that it will only produce junk.
dragonwriter 3y ago
> As someone with a lowly 10gb card sdxl is beyond my reach with a1111 it seems SDXL reportedly works at below 8GiB in A1111 with --low-vram, and at 8GiB to anything short of 16GiB with --med-vram-sdxl, and 16GiB and up with no options. > but I can't make anything but garbage with it in automatic. If you aren't getting out of memory errors with SDXL but the output sucks, its probably not a VRAM problem. The most likely thing, IME, is using the SDXL base model or another checkpoint without a baked VAE but still having A1111 configured to use an SD1.x VAE (or using one with a baked VAE but having A1111 configured to override it.) SDXL needs an SDXL-specific VAE, but A1111 doesn't bundle one, IIRC, you need to download it separately.

thot_experiment 3y ago

I haven't been paying attention for a few months, is there a lot of development happening around SDXL or are people still mostly focused on 1.5? My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data, is that bearing out?

GaggiX 3y ago
>My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data Where do you read that SDXL has worse training data? They didn't disclose what the model was trained on like the previous models.
Veraticus 3y ago
Most people (and models) still use 1.5 because of hardware and performance issues with SDXL.
dragonwriter 3y ago
> I haven't been paying attention for a few months, is there a lot of development happening around SDXL or are people still mostly focused on 1.5? There's been a lot happening on SDXL, yes. > My expectation was that SDXL would probably not see wide adoption for a while because it's hard to make up for the worse training data, is that bearing out? What worse training data?
- thot_experiment 3y ago
  > There's been a lot happening on SDXL, yes. Nice! Care to share any projects/advancements/gens you've found particularly compelling if you have anything handy? > What worse training data? I don't know this, but I think it's a pretty safe assumption given the state of 2.0/the political climate around this stuff, along with the comparative lower diversity of gens I've seen come out of SDXL. I haven't seen anything to the contrary but I'd love to be wrong.

iLoveOncall 3y ago

I've used SDXL with a 3080 (10GB) mostly without issues. You have to give some command line parameters when launching it to reduce memory use. > --medvram-sdxl --no-half-vae

Filligree 3y ago
"--no-half-vae" doesn't reduce memory usage, it forces A1111 to use 32-bit floats for the VAE decoding.
- dragonwriter 3y ago
  --no-half-vae, IIRC, is required for the stock sdxl vae model because otherwise it frequently produces errors. I believe there’s a half-precision fixed VAE floating around and baked into many SDXL-derived checkpoints that avoids this problem.

DrSiemer 3y ago

Runs just fine on my 8GB card. You probably did not swap the VAE. Without that it will only produce junk.

dragonwriter 3y ago

> As someone with a lowly 10gb card sdxl is beyond my reach with a1111 it seems SDXL reportedly works at below 8GiB in A1111 with --low-vram, and at 8GiB to anything short of 16GiB with --med-vram-sdxl, and 16GiB and up with no options. > but I can't make anything but garbage with it in automatic. If you aren't getting out of memory errors with SDXL but the output sucks, its probably not a VRAM problem. The most likely thing, IME, is using the SDXL base model or another checkpoint without a baked VAE but still having A1111 configured to use an SD1.x VAE (or using one with a baked VAE but having A1111 configured to override it.) SDXL needs an SDXL-specific VAE, but A1111 doesn't bundle one, IIRC, you need to download it separately.