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
Add EventsPerLumi for relvals workflows and prod-like concurrentLS relvals #29318
Conversation
…concurrentlumi relvals
The code-checks are being triggered in jenkins. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29318/14396
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages: Configuration/PyReleaseValidation @chayanit, @cmsbuild, @wajidalikhan, @pgunnell, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@makortel @Dr15Jones @silviodonato @fabiocos @chayanit |
Doing more comprehensive testing of jobs with multiple LuminosityBlocks makes sense to me. The down side, is without concurrent lumis (and even with but with module's that inhibit efficient use of concurrent lumis) the multi-thread efficiency of the jobs will descrease. Say we use 4 threads and 5 events per lumi. So on average each thread only processes 1 event and then has to wait for all other threads to finish (because of synchronization on the lumi boundary). |
Hi @Dr15Jones |
please test workflow 1302.18,1304.18,1302.181,1304.181 |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
test parameters |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+upgrade |
Do you have comments @chayanit @pgunnell @wajidalikhan ? |
+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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is to add an option to set EventsPerLumi in relvals. Normally, GEN relvals will set EventsPerLumi = EventsPerJobs. Setting can be done in 2 ways:
process.source.numberEventsInLuminosityBlock
in relvals workflow, orrunTheMatrix.py --numberEventsInLuminosityBlock
(overwrite "1." if both options exist)In addition, 2 additional relvals (1302.181 and 1304.181) are added. They are prod-like 2018 production with concurrentLumis enable.
RelVals: Link
PR validation:
runTheMatrix.py --what standard -l 1302.18,1304.18,1302.181,1304.181 -t 4 --wm init
==> only concurrentLumis workflows have EventsPerLumi = 5 (as set in cmsDriver)
runTheMatrix.py --what standard -l 1302.18,1304.18,1302.181,1304.181 --numberEventsInLuminosityBlock 20 -t 4 --wm init
==> All workflows have EventsPerLumi = 20
if this PR is a backport please specify the original PR and why you need to backport that PR: