This repository was archived by the owner on Nov 27, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to introduce batch processing of images.
Some background, support for batch prompt processing was added, however this has some fallbacks IMO, as it stands now if you create a batch of 4 images, it will process the prompt etc once, however the expensive parts really gain no benefit, you just end up waiting 4x longer for 4 images, and you can only run a Batch on one set of Scheduler settings
I propose a solution to this and also provide more options for batch results.
Adding a new
DiffuseBatchAsync
method in the base diffusers that returns a collection of tensors, this method will take in a newBatchOptions
parameter, this we can use to provide all the parameter for the batch type we want to runEach image will be returned to the user as its generated, so no long wait, and can be canceled without losing the images already generated.