-
Notifications
You must be signed in to change notification settings - Fork 7
Updated run requirements. #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the run requirements for the HPL benchmark documentation, reorganizing sections and expanding testing details. The changes improve the structure and clarity of the documentation while adding more specific requirements for benchmark execution and validation.
- Reorganized documentation sections with "How to run" moved before "How to validate"
- Added detailed testing requirements including single-node vs multi-node configurations and memory saturation guidelines
- Enhanced run rules with specific optimization guidelines and compiler requirements
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
HPL/README.md
Outdated
|
|
||
| ## Tests | ||
|
|
||
| Testing will include single-node and multi-node configurations. The single-node test exposes the compute capability of the unit by reducing the effect interconnect at a node level, while the multi-node test measures the overall system performance and exposes scaling and interconnect bottlenecks at the system level. In general, the problem size (`N`) should be tuned to saturate at least 80% of available system memory so that maximum peak performance would be acheived. |
Copilot
AI
Sep 16, 2025
•
edited by gbetrie
Loading
edited by gbetrie
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a grammatical error: 'reducing the effect interconnect' should be 'reducing the interconnect effect' or 'reducing the effect of interconnect'.
| Testing will include single-node and multi-node configurations. The single-node test exposes the compute capability of the unit by reducing the effect interconnect at a node level, while the multi-node test measures the overall system performance and exposes scaling and interconnect bottlenecks at the system level. In general, the problem size (`N`) should be tuned to saturate at least 80% of available system memory so that maximum peak performance would be acheived. | |
| Testing will include single-node and multi-node configurations. The single-node test exposes the compute capability of the unit by reducing the interconnect effect at a node level, while the multi-node test measures the overall system performance and exposes scaling and interconnect bottlenecks at the system level. In general, the problem size (`N`) should be tuned to saturate at least 80% of available system memory so that maximum peak performance would be acheived. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Updated run requirements.