lllyasviel / lllyasviel/stable-diffusion-webui-forge
controlnet `Batch` workflow needs to be efficient
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
The controlnet Batch method is set by Batch size in Forge while the official A1111 use Batch count to do it. The Forge way will accumulate the vram, it can't handle a lot of Batch images, e.g., for my 16GB RTX 4080, it can do ~30 controlnet Batch images, but no way to handle 150 Batch images. The official A1111 handle it without any problems. I think the Forge should follow the official A1111 way to do it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the controlnet Batch method and compare its Batch size handling with the official A1111 Batch count behavior. Verify that processing around 150 images does not accumulate VRAM beyond the available 16GB, while preserving the expected batch results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100