-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
speed up shared-hits cleaning in TrackerSeedCleaner
#47023
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47023/43140 |
A new Pull Request was created by @missirol for master. It involves the following packages:
@cmsbuild, @jfernan2, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
|
+1 |
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. @mandrenguyen, @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
CMSHLT-3366 discusses one event with long processing time at HLT (~9 minutes online). It looks like most of this time is spent in the method
RedundantSeedCleaner::clean
(which is called fromRedundantSeedCleaner::define
, which in turn is called fromTrackerSeedCleaner::clean
).This PR includes small technical changes to make the method in question faster (
RedundantSeedCleaner
is removed, and the relevant function is integrated inTrackerSeedCleaner
itself). In the simplified example in [1] based on CMSHLT-3366, the instance in question ofTSGFromL2Muon
takes ~700 seconds pre-PR, and ~300 seconds post-PR.Merely technical. No changes to physics outputs expected.
PR validation:
Using [2] to print properties of the seeds post-cleaning using the test in [1], one gets exactly the same printout before and after this PR.
[1]
[2]
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:
N/A