Add core-to-core latency results for Grace CPU #181
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
preview available: https://docs.tds.cscs.ch/181 |
RMeli
approved these changes
Jul 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds core-to-core latency diagrams for within one Grace CPU and between the first cores on each CPU. I have full data, but I find plotting all 288 cores is near unreadable, so opted for the simplified results across sockets.
The single CPU SVG is relatively big for what it is (~800kB). The original PDF is significantly smaller (65kB) but mkdocs does not render it as an inline image. A PNG is also close to 1MB, even when optimized (lower resolution would likely help, but it's not super high resolution anyway).