Codechange: Performance improvement in k-d tree FindNearest() #7608
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 improvement is small, around 4-8%.
I have tested it on a few different map by calling the
FindNearest()
function on every tile of a map, and counting the number of theFindNearestRecursive()
calls.The version of this PR draft contains the old and the new
FindNearest()
functions, and an additional console command 'count_calls' to test the improvement.