Optimize HPL and MPICH further #70
Merged
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.
HPL spends the majority of its execution time inside the BLAS implementation, so these changes affect mainly slower processors such as in-order ones.
Note that link-time optimization (i.e. the
-flto
option) increases both build time and memory consumption during linking by a non-trivial amount. As a reminder, the-march=native
parameter behaves differently on AArch64 and x86-64, for example, especially with older compilers such as GCC up to and including version 14, so ideally we would combine it with-mtune=native
as futureproofing. However, in my experiments it didn't lead to any further significant performance difference, while all 20 runs that I tried failed the residual check, so I decided to omit it.I benchmarked my changes on a Radxa Orion O6 board by doing 20 runs with the
Qs
parameter set to12
andblis_configure_options
- tocortexa57
. Here are my results:In other words, an approximately 1.69% improvement. For comparison, on an AMD Ryzen 9 5900X-based machine with 64 GiB RAM there was no significant difference.