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
Simple configuration testing #20466
Simple configuration testing #20466
Conversation
AddIntsProducer is being used in timing tests so better to use more performant getBy call.
Added an Analyzer that gets IntProducts. This is used in infrastructure timing tests.
The script can read the log file of a job that used the Tracer with 'dumpPathsAndConsumes' turned on. From that log file it can create a new configuration file which has the same module topology but with the modules all replaced with 'trivial' counterparts.
The code-checks are being triggered in jenkins. |
please test |
+1 |
@fwyzard you can use this to test the maximum throughput for the HLT topology. |
+code-checks |
The tests are being triggered in jenkins. |
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Framework @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready There are some workflows for which there are errors in the baseline: Comparison Summary:
|
+1 |
Items to be used to test configurations made up of 'trivial' modules.
This includes a new script edmTracerLogToSimpleConfig.py which can read a job log which
containers Tracer output and then create a new configuration with the same module topology
but with the modules replaced with 'trivial' instances.
This allows for finding performance bottlenecks in the framework for standard configurations topologies.