Performance improvements: moving from data organized in an Array of Structures (AoS) to an organization of Stucture of Arrays (SoA) #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.
This PR moves from having data nodes data organized in an Array of Structures (AoS) to an structure of Arrays (SoA), meaning that in practical terms we use an array of primary data-types instead of an array of centroids ( struct ).
The impact of this change on both reads/writes can be described by the following table and chart. We see up to 180% less CPU time spent on the same operations.
Raw benchmark outputs:
Before performance improvements:
After performance improvements:
Measuring Giga-FLOPS per cycle per core per second
We can use the fp_arith_inst_retired.scalar_double event (Number of SSE/AVX computational scalar double precision floating-point) to get the Giga-FLOPS per cycle per core per second for both branches...
Giga-FLOPS per cycle per core per second master branch
Giga-FLOPS per cycle per core per second perf.qsort.central branch