reorder moves for better cache locality #300
Closed
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.
need to merge onto benchmark and, uh, benchmark, this should bump up the percent of BlockStateInterface lookups that are in the same cached chunk / region as the previous by a couple percent, i anticipate. it won't actually increase that metric in benchmark, because every movement gets data from both the source chunk and the destination chunk, but it will improve the cache locality of the adjacent chunks by going on counterclockwise order like this (instead of random). or at least i hope it will.