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
Improve DD4hep workflow perf, step 2: Remove regex from Phase 1 trackerRecoMaterial.xml #32511
Conversation
…lysis/data/trackingMaterialGroups_ForPhaseI.xml, which had identical names as the SpecPar blocks in trackerRecoMaterial.xml (!!). This file was added few months ago to all geometry scenarios (why is that? as it is only used for testing materials anyway). It has a very big impact on DD4hep Run3 workflow perf. The underlying issue is that in DetectorDescription/DDCMS, when processing XMLs files for DD4hep, all SpecPar sections with same name are merged together. This results in lookups in (extremely heavy !) paths of trackingMaterialGroups_ForPhaseI.xml being made while searching for TrackerRadLength, despite TrackerRadLength not being defined in those files anyway!
…d4hep (why is there a duplicated file??)
…erial.xml. I presume the pixfwdblade.*Zplus had been done to distinguish from the pixfwdblade[0-9]:PixelForwardBlade. But this is not recessary, because the pixfwdblade[0-9]:PixelForwardBlade are not called in any geo scenario where data/PhaseI/trackerRecoMaterial.xml is used.
…these paths are not looped over when not needed anyway, hence this commit has no effect on workflow perf).
… has very small, but non-null, impact on perf.
…erial.xml. Very significant perf improvement. This version is compatible to work on both DDD and dd4hep cases.
…ngMaterialGroups_ForPhaseI.xml, version working for both DDD and dd4hep.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32511/20450
|
A new Pull Request was created by @ghugo83 for master. It involves the following packages: Geometry/TrackerRecoData @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Phase I (Run 3) XML files must be given a new version number when changed. |
Ok, will duplicate that file then. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32511/20464
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-258ecf/11800/summary.html DAS Queries failed Comparison SummarySummary:
|
@ghugo83 The name for the |
@cvuosalo , are you sure about this SimTracker/TrackerMaterialAnalysis/data/? Is it a part of DB payload? |
+1 Let us merge this PR and if extra updates are needed implement in the following PR, because we should be able to see effect of these updates. @kpedro88 , please, have a look. |
+upgrade |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@ghugo83 there is a conflict |
@silviodonato I'm following, it looks merging went fine . If something is breaking we can revert to rebase and restart the build |
Thanks, sorry was travelling. I will just rename SimTracker/TrackerMaterialAnalysis/data/v1/trackingMaterialGroups_ForPhaseI.xml to SimTracker/TrackerMaterialAnalysis/data/trackingMaterialGroups_ForPhaseI/v1/trackingMaterialGroups_ForPhaseI.xml as suggested, but that is just a renaming. |
|
@civanch |
This also has big impact on perf in the DD4hep workflow, and no diff in perf in the DDD workflow.
NB 1: I have directly modified Geometry/TrackerRecoData/data/PhaseI/trackerRecoMaterial.xml, which is the only trackerRecoMaterial.xml for Phase 1.
If this file should be rather duplicated to be changed, please let me know and I will just move it.
NB 2: To avoid merge conflicts, this branch is on top of #32505 , which should be merged first.
@ianna @civanch @cvuosalo