DEBUG: Hardware benchmark on GitHub Actions (CPU)#439
Closed
mmcky wants to merge 4 commits into
Closed
Conversation
- Add benchmark-hardware.py script for CPU/GPU performance testing - Install JAX CPU version for comparison - This PR tests standard GitHub Actions runner performance
- Update benchmark-hardware.py to save results to JSON - Update benchmark-jupyter.ipynb to save results to JSON - Update benchmark-jupyterbook.md to save results to JSON - Add CI step to collect and display benchmark results - Add CI step to upload benchmark results as artifact
Contributor
Author
|
Closing as no longer required. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose
This PR runs hardware benchmarks on the standard GitHub Actions runner (CPU-only) to compare performance against the RunsOn GPU runner.
Benchmarks Included
Comparison
Results from this PR should be compared with PR #437 which runs the same benchmarks on RunsOn (GPU).
Note
This is a debugging PR to investigate performance differences. It should not be merged.