Live data from Hacker News

Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

github.com

11–20 of 151 posts

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#11
For everyone about to comment on the garbage in the commit:

It looks like the committer made their changes in the top commit, then merged the updated CompViz StableDiffusion change set on top of it for some reason. That's where the license change, rick astley image, etc come from.

And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter.

Here's the code that does it:

https://github.com/CompVis/stable-diffusion/blob/main/script...

And here's what it looks like:

https://twitter.com/qDot/status/1565076751465648128

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#13

Unfortunately the author of this PR decided to include garbage like this [1] in it, so this PR is pretty useless. [1] https://github.com/basujindal/stable-diffusion/pull/103/file...

I just reminded "clean room design" technique: https://en.m.wikipedia.org/wiki/Clean_room_design

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#14
post #5

How much VRAM was previously required?

Looks like 10GB in the README[0] for a 512x512 image - though the fork[1] from the repo in this PR claims to be able to work with as little as 4GB VRAM.

[0] https://github.com/CompVis/stable-diffusion#stable-diffusion [1] https://github.com/basujindal/stable-diffusion#txt2img

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#15

Unfortunately the author of this PR decided to include garbage like this [1] in it, so this PR is pretty useless. [1] https://github.com/basujindal/stable-diffusion/pull/103/file...

I just reminded "clean room design" technique: https://en.m.wikipedia.org/wiki/Clean_room_design

Yeah, reminds me of the old freedoom WADs situation

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#16

Unfortunately the author of this PR decided to include garbage like this [1] in it, so this PR is pretty useless. [1] https://github.com/basujindal/stable-diffusion/pull/103/file...

Seems like author did his work on a different fork and pushed to this one, which included all changes from the other fork...

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#17
post #12
post #5

How much VRAM was previously required?

I can generate a 768x896 pixels image on an RTX 3090, using 23.4/24GB

How does the content of the images look compared to the same prompt and seed for 512x512? I ask because when I make 768x896 with M1 MAX the resulting image is less coherent, more noisy, and or has repeating subject matter, nothing really usable unlike 512x512.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#18

For everyone about to comment on the garbage in the commit: It looks like the committer made their changes in the top commit, then merged the updated CompViz StableDiffusion change set on top of it for some reason. That's where the license change, rick astley image, etc come from. And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. Here's…

But what is the correct git command to ignore all that?

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#19
post #7

Almost impossible to pinpoint what changed thanks to thousands of lines of completely irrelevant changes and shitty commit messages. It seems the only changeset that might be relevant out of +2,273 -1,531 is the +11 -7 from https://github.com/basujindal/stable-diffusion/pull/103/comm... ? Does it even work?

As a learning opportunity for people like me, what does a good PR look like for a large change?

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#20
post #19
post #7

Almost impossible to pinpoint what changed thanks to thousands of lines of completely irrelevant changes and shitty commit messages. It seems the only changeset that might be relevant out of +2,273 -1,531 is the +11 -7 from https://github.com/basujindal/stable-diffusion/pull/103/comm... ? Does it even work?

As a learning opportunity for people like me, what does a good PR look like for a large change?

You don’t make large change PRs.
Post reply on HN