-
Notifications
You must be signed in to change notification settings - Fork 34
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
change batch count of 4 to batch size of 4 instead #7
Comments
Great suggestion! On my lowly gaming PC, a batch size of 4 with 768 images turns out to run out of memory. I need a 4090 😆 What I think I'd probably do is add both "batch size" and "batch count" as default bot settings (just like the 512 or 768 size is now). That way each person using the bot would be able to customize as they see fit. |
If you'd like to try this out, I've opened a PR and branch with the added updates: #8 Since you can build from source, you can do a:
That will build the bot version from the proposed changes. It adds a new bot configuration that allows you to update the balance between count/size such that it results in a total of four images. You can summon the configuration message by the Discord command Let me know if this works for you. I've tested it myself, and it seems good, but maybe you run into something. |
2} |
Right now the bot creates 4 images one by one as "Batch Count" is set to 4. If you change it to be the "Batch Size" set to 4 instead (and batch count back to 1) Automatic1111 will make all 4 images at once. instead of one by one. This should be a faster way to get the 4 images. Don't know if that throws a wrench in any logic but I did some tests on my system and to generate 4 768x768 it takes 45 seconds using "batch count" but using "batch size" it only takes 40 seconds (Euler a/20 steps, cfg 8, note that 512x512's speed discrepancy is smaller and only 2-3 seconds)
The text was updated successfully, but these errors were encountered: