Skip to content
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 put interface using EDPutToken #20595

Merged
merged 9 commits into from Sep 22, 2017
Merged

Add put interface using EDPutToken #20595

merged 9 commits into from Sep 22, 2017

Conversation

Dr15Jones
Copy link
Contributor

As a preliminary to improving the performance of the 'put' system, we introduce the use of the EDPutToken.

produce can not directly return an EDPutToken since we need to be able to call 'setBranchAlias' on the returned value. Using a SetBranchAlias class that can be converted to a EDPutToken solves the problem.
Event, LuminosityBlock and Run now accept a EDPutToken as an argument to 'put'.
This is the first step to a speedup of the put system.
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20595/835

Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/PR-20595/835/git-diff.patch
e.g. curl https://cmssdt.cern.ch/SDT/code-checks/PR-20595/835/git-diff.patch | patch -p1

You can run scram build code-checks to apply code checks directly (this will soon be required for PRs to be considered)

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20595/836

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones (Chris Jones) for master.

It involves the following packages:

FWCore/Framework
FWCore/Integration
FWCore/Utilities

@cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @felicepantaleo, @ebrondol, @wddgit, @makortel this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor Author

please test

@Dr15Jones
Copy link
Contributor Author

+1

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20595/23117/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 9 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2649068
  • DQMHistoTests: Total failures: 339
  • DQMHistoTests: Total nulls: 8229
  • DQMHistoTests: Total successes: 2640311
  • DQMHistoTests: Total skipped: 189
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 14 edm output root files, 26 DQM output files

@davidlange6
Copy link
Contributor

please test
(are these reco differences real?)

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 21, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23139/console Started: 2017/09/21 12:17

@Dr15Jones
Copy link
Contributor Author

@davidlange6 I do not see any reasonable way this change could cause a difference for reco. Non of the code added changes how any of our present code works. It could shift things in memory a bit, but we hope our results are not dependent upon exact memory addresses used (although anyone sorting by pointer addresses might see a difference).

@Dr15Jones
Copy link
Contributor Author

@davidlange6 @slava77 do either of you know how to determine what the comparison system thought was different?

@slava77
Copy link
Contributor

slava77 commented Sep 21, 2017

Follow the links for "Comparison is ready" -> "See Comparison Results" -> "validateJR" -> "logRootQA.log"
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_9_4_X_2017-09-19-1100+20595/22620/validateJR/logRootQA.log

JR results differ 9 all_OldVSNew_TTbar14TeV2023D17wf20034p0
step up and look in this directory:
changes are in outputs of hgcalLayerClusters.

HOWEVER, before worrying much about this, go to the summary of the test made
#20595 (comment)
to see that the PR was ahead of any available IBs when submitted.
It's nice to be pedantic about being in sync with the head of master, but the cost of it is inability to test the change until a new IB ahead of that PR appears.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20595/23139/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2654399
  • DQMHistoTests: Total failures: 232
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2653978
  • DQMHistoTests: Total skipped: 189
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 14 edm output root files, 26 DQM output files

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 2ca3a4d into cms-sw:master Sep 22, 2017
@Dr15Jones Dr15Jones deleted the putToken branch October 10, 2017 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants