Can this be run without colab Pro? (High vram)
Fast-stable-diffusion colabs, +25% speed increase and memory efficient
11–20 of 24 posts
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#12any differences in output or they are identical with the same prompt and seed?
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#13Would be much better if these changes were a branch on the starting repo rather than entire refactors with many changes.
There are pros and cons to each of these Stable Diffusion hacks (usually time/memory/usability tradeoffs) so it's not correct to merge it back.
Which is why it would be a branch, no?
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#14Can this be run without colab Pro? (High vram)
The un-optimized version runs in a free notebook, but you hit the vram cap if you try to increase image resolution or generate more than one image at a time.
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#15Earlier quoted context omitted.
Run it on a burner Gmail account
In addition to having a google account without any sensitive info, running everything in VMs locally should become a standard practice
Colab runs everything remotely unless you point it at a locally installed Jupyter runtime.
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#16I love StableDiffusion, and these projects are so exciting. But. Isn't this the new equivalent of downloading and running a shell script WHICH YOU HAVE NO IDEA WHAT IT DOES? This colab notebook asks for me to give it access to my GDrive. If any of the sd code were modified from the original SD codebase (as I would expect it to be, this is a FORK afterall!) then why couldn't it pull certain anything it wants from my G…
Everything about the SD ecosystem feels like... I'm not sure. It seems like there are tons of different small, uncoordinated efforts, all of which have either no documentation or large plaque install scripts, and then it's all python at the bottom with all of the joys of it's package ecosystem.
And then all of these versions where they're so super smart and want access to my GD and an API token to some account of mine? Christ, it would be so, so, so easy to weaponize one of these, add some screenshots and "beat" the original and harvest some Google Drive goodies.
In a, I guess I'll say, less frustrating world... there'd be a Nice or Guix expression and it would be relatively trivial to just launch it anywhere Linux and GPU exists.
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#17These guys claim a 50% speedup with a similar approach:
https://www.reddit.com/r/StableDiffusion/comments/xmr3ic/spe...
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#18Would be much better if these changes were a branch on the starting repo rather than entire refactors with many changes.
There are pros and cons to each of these Stable Diffusion hacks (usually time/memory/usability tradeoffs) so it's not correct to merge it back.
And in this case it seems like mostly an implementation detail - it could just be a flag to enable, or enabled whenever it detects running on colab.
Re: Fast-stable-diffusion colabs, +25% speed increase and memory efficient
#19I love StableDiffusion, and these projects are so exciting. But. Isn't this the new equivalent of downloading and running a shell script WHICH YOU HAVE NO IDEA WHAT IT DOES? This colab notebook asks for me to give it access to my GDrive. If any of the sd code were modified from the original SD codebase (as I would expect it to be, this is a FORK afterall!) then why couldn't it pull certain anything it wants from my G…
Run it on a burner Gmail account
How does one make a burner Gmail account these days? Last I tried, a unique phone number was required.