-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Run modules concurrently during global begin transitions #18451
Run modules concurrently during global begin transitions #18451
Commits on Apr 21, 2017
-
Add test for getting a product made only at end transitions
Test getting products that are only made at end transitions during begin transitions and during event.
Configuration menu - View commit details
-
Copy full SHA for cd43b75 - Browse repository at this point
Copy the full SHA cd43b75View commit details
Commits on Apr 23, 2017
-
Determine items to get for all transitions, not just event
Changed the interface to modules to allow querying about which data products it consumes for all transition types.
Configuration menu - View commit details
-
Copy full SHA for 489070e - Browse repository at this point
Copy the full SHA 489070eView commit details -
Principal knows if at end transition
In the future, the Principal will need to know if it is at an end Run or end LuminosityBlock transition so we prefetch items that are only made at the end transition on the end transition.
Configuration menu - View commit details
-
Copy full SHA for 769a2e7 - Browse repository at this point
Copy the full SHA 769a2e7View commit details -
Only emit Event signals during Event processing
Prefetching will be used for non-Event transitions so we need to be certain to only send signals from the ActivityRegistry meant for the Event during Event processing.
Configuration menu - View commit details
-
Copy full SHA for 582cc5b - Browse repository at this point
Copy the full SHA 582cc5bView commit details -
Update NoProcessProductResolver's cache at end transition
Requesting a data product without using a process name can result in different results based on if the request happens before the end transition. The reason is if the module in the job only puts its data into the Principal at an end transition but the source contains a related data product from a previous process. Requesting before the end transition would return the previous process data product, while waiting to request at end will return the newly created data product. To accommodate prefetching of data products from Run and LuminosityBlocks, we need to reset the cached lookup information at end transition to allow the newly requested item to be obtained.
Configuration menu - View commit details
-
Copy full SHA for e49a8b3 - Browse repository at this point
Copy the full SHA e49a8b3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 50fa04f - Browse repository at this point
Copy the full SHA 50fa04fView commit details
Commits on Apr 24, 2017
-
EventProcessor runs modules in global begin transitions concurrently
Use new async version for global begin Run and Luminosity transitions.
Configuration menu - View commit details
-
Copy full SHA for fe9e05e - Browse repository at this point
Copy the full SHA fe9e05eView commit details -
Modules in SubProcesses are run concurrently on global begin transitions
Extended the concurrent running of modules on global begin transitions to SubProcesses. Child SubProcesses are also run concurrently.
Configuration menu - View commit details
-
Copy full SHA for d677356 - Browse repository at this point
Copy the full SHA d677356View commit details