⚡️ Speed up method BlipImageProcessor.postprocess
by 51%
#11666
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.
📄 51% (0.51x) speedup for
BlipImageProcessor.postprocess
insrc/diffusers/pipelines/blip_diffusion/blip_image_processing.py
⏱️ Runtime :
201 milliseconds
→133 milliseconds
(best of27
runs)📝 Explanation and details
Here’s a faster, more memory-efficient rewrite while preserving all return values and function signatures. The optimizations address.
.cpu()
calls when already on CPUOptimizations made:
.cpu()
calls and ensured direct use of.contiguous()
before.numpy()
to avoid memory bottlenecks on non-contiguous tensors.[..., 0]
indexing, never triggers for RGB).astype("uint8", copy=False)
to avoid unnecessary array copying during data type conversion..clamp_()
for in-place operations to reduce memory and allow for better memory reuse.size
default initialization outside the function call for better micro-optimization and readability.No changes to logic, outputs, or external side-effects or comments.
✅ Correctness verification report:
🌀 Generated Regression Tests Details