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
Backport of #22935 to 93X (Add a flag to prevent storage of LHEXMLStringProduct) #22947
Conversation
A new Pull Request was created by @fabiocos (Fabio Cossutti) for CMSSW_9_3_X. It involves the following packages: GeneratorInterface/LHEInterface @cmsbuild, @efeyazgan, @perrozzi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+code-checks |
@kpedro88 @perrozzi @efeyazgan FYI, this needs to be tested on some working workflow |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
I confirm that I can run succesfully with this commit under 93x and I observe a reduction of the output file size. approving |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos, @kpedro88 (and backports should be raised in the release meeting by the corresponding L2) |
merge |
LHEXMLStringProduct is no more really used in production, and it is creating memory issues keeping on hold production in 93X. This PR adds a boolean flag as untracked parameter to activate/deactivate the storage of the xml output into the product, setting the default to "false" (i.e. do not store).
With the opportunity I fixed also the ExternalLHEAsciiDumper analyzer that was supposed to extract the xml file out of the edm root output, and that was no more working.
Both the "false" and "true" option have been tested in wf 512 (10 events), with a visible reduction of the final file size (84kB vs 112kB), and when the option was true the dumper was used to extract the xml file (216 kB after de-compression), proving that is again functional.
Tested in master (10_2_X), wf 512.0 not functional in 9_3_8.
Backport of #22935 (only changes in that PR, rest of the package left unchanged)