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
Migrate EventFilter from boost::format to {fmt} #30855
Migrate EventFilter from boost::format to {fmt} #30855
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30855/17212
|
A new Pull Request was created by @fwyzard (Andrea Bocci) for master. It involves the following packages: EventFilter/EcalRawToDigi @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Just a suggestion, now that |
@cmsbuild, please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@rchatter |
@pieterdavid @robervalwalsh |
shouldn't you also subscribe to be notified about changes in this package? |
Yes, it seems we forgot to include this package in our list - I submitted cms-sw/cms-bot#1345 to fix that. Thanks for spotting this. I'm not very familiar with the syntax of {fmt}, but at first sight the changes look sensible. |
I migrated |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30855/17272
|
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Hi all, Sorry for the delay in following up. I have cross-checked with ECAL RECO experts the changes made in this file: EventFilter/EcalRawToDigi/plugins/MatacqProducer.cc . While am not aware of this library fmt, this change seems to Best, |
Comparison is ready Comparison Summary:
|
I ran a quick timing test on
|
What does something like igprof say for how much time is spent inside the library?
On Jul 24, 2020, at 10:35 AM, Joosep Pata <notifications@github.com<mailto:notifications@github.com>> wrote:
I ran a quick timing test on 1302.18 and interestingly, with this PR enabled it's is very slightly slower. This is somewhat surprising, given the reportedly good performance of fmt::format. Let me know if I missed something.
$ grep "TimeReport event loop CPU/event" */1302*/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log*
new/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log:TimeReport event loop CPU/event = 5.321165
new/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log2:TimeReport event loop CPU/event = 5.281827
new/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log3:TimeReport event loop CPU/event = 5.340586
orig/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log:TimeReport event loop CPU/event = 5.256085
orig/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log2:TimeReport event loop CPU/event = 5.245805
orig/1302.18_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18/step3_ProdTTbar_13UP18+ProdTTbar_13UP18+DIGIUP18PROD1+RECOPRODUP18+MINIAODMCUP18+NANOPRODUP18.log3:TimeReport event loop CPU/event = 5.275022
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#30855 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGPFQ2XOHMRNNYDHJQ5ANDR5FBV3ANCNFSM4PD2P6VQ>.
|
+1
It was suggested by Slava that event-level timing is not meaningful to 1%. I looked at module-level timing of the |
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 |
PR description:
Migrate from
boost::format
tofmt::format
orfmt::sprintf
.