Small bloom render pass optimization#7104
Merged
mvaligursky merged 1 commit intomainfrom Nov 13, 2024
Merged
Conversation
mvaligursky
added
performance
willeastcott
approved these changes
Nov 12, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The bloom uses a series of downscaling and upscaling render passes to blur.
Instead of executing more costly 13-samples downscaling at all time, use just a single sample box filter for downscaling from full to half res, which is the most costly pass. No visible difference to the quality.
Cost of 4k rendering of Post-Processing example on apple m1 max:
before: 4.4ms
now: 4.2ms