Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VRAM Issue #5

Open
Andreas48624 opened this issue Nov 8, 2022 · 1 comment
Open

VRAM Issue #5

Andreas48624 opened this issue Nov 8, 2022 · 1 comment

Comments

@Andreas48624
Copy link

When swapping schedulers it will use approximately 6GB of VRAM

Also need to close and reopen the GUI after generating an image as it keeps the VRAM used

@quickwick
Copy link
Owner

I'm not sure I understand the problem here. Loading any scheduler is what uses up RAM. I can generate multiple images without needing to close and reopen the GUI. That was one of the purposes of the GUI, to be able to easily generate multiple images in a row without having to reload the scheduler each time (unlike the original script examples I based this off of).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants