Add timing profiling benchmark for detector simulation performance analysis #207
+594
−1
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
…alysis This benchmark measures computational performance of detector simulation by profiling time spent in different detector regions during Geant4 stepping. - Add benchmarks/timing_profiling/ with run_profile.sh and analysis scripts - Integrate with CI/CD pipeline via .gitlab-ci.yml - Uses PerformanceProfileSteppingAction plugin to collect timing data - Generates annotated plots showing computational hotspots in detector geometry - Outputs CSV summaries of timing by detector region Requires: eic/npsim#35 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 benchmark measures computational performance of detector simulation by profiling time spent in different detector regions during Geant4 stepping.
Requires: eic/npsim#35
🤖 Generated with Claude Code
Briefly, what does this PR introduce?
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?