Implement GPU vs CPU comparison for HLT pixel tracking heterogeneous products in patatrack workflows #49340
Conversation
|
enable gpu |
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49340/46712
|
|
@cmsbuild, please test |
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@AdrianoDee, @DickyChant, @antoniovagnerini, @ctarricone, @gabrielmscampos, @miquork, @nothingface0, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 Size: This PR adds an extra 56KB to repository Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
NVIDIA_T4 Comparison SummarySummary:
|
|
+dqm |
|
+pdmv |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @mandrenguyen, @ftenchini (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
This PR is a quick follow-up upon #49105.
Thanks to the recently merged PR #49303 we are now saving into the
HLTDebugRAWandHLTDebugFEVTevent content definitions alsohltSiPixelRecHitsSoA*,hltPixelTracksSoA*andhltPixelVerticesSoA*.This puts us in a position to include in the
HLTHeterogeneousMonitoringSequencedefined in #49105 all the various monitoring modules for the pixel rechits, tracks and vertexSoAs. This is carried out in commit e8814ac.I profit of this PR to fix some typos / oddities in commit eaef3cd as well as adding a harvesting step for the
@hltGPUvsCPUsequence in commit 0e98d60.PR validation:
Run successfully:
runTheMatrix.py --what gpu -l 17034.402 -t 4 -j 8 --ibeosand checked that the desired output plots are available (see for example here).
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport, it won't be backported.