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
Sleeping modules #22885
Sleeping modules #22885
Conversation
Created a series of Modules which call usleep in order to allow scale testing without consuming the entire system.
If no module uses the global begin run transition then the script was unable to find the number of streams. Now the script also looks at the source transitions to find the number of streams.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22885/4266 |
please test |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Concurrency @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 Comparison Summary:
|
@fabiocos ping |
Changes in the comparison are clearly induced by the other PRs included (GT in particular) @Dr15Jones this is essentially a job emulator to study multi-threading behaviour just introducing artificial delays without real CPU being consumed, right? I understand this will not enter into a production workflow |
Correct |
+1 |
Created modules which do usleep based on a configuration parameter. These can be used to do simple timing studies without requiring lots of CPU resources.