[rtextures] Optimize ImageClearBackground and ImageDrawRectangleRec with doubling strategy #5363
+9
−5
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.
Background
I use the
ImageDraw*functions in a slightly unconventional way, and while doing so I noticed thatImageClearBackgroundis over an order of magnitude slower than simply callingImageDrawRectangleover the entire image.Issue
ImageClearBackgroundcallsmemcpyonce per pixel and doesn’t take advantage of the fact thatmemcpyis very fast when copying large contiguous blocks of memory. As a result, it incurs the overhead of a function call for every pixel.Fix
Instead of copying one pixel at a time, we can iteratively copy the data that has already been written to the image buffer, effectively doubling the amount of initialized data with each iteration. This reduces the number of
memcpycalls fromO(N)toO(log N).I applied the same optimization to
ImageDrawRectangleRec. The improvement there is smaller because only the first row is written pixel-by-pixel.Result
15-20 times faster execution times on my PC.