This involves making the service stream-aware. However, thread-safety is likely not a problem because creating the engines is done only at configuration time. Moving to using TBB concurrent containers could be helpful.
#1 Updated by Kyle Knoepfel over 2 years ago
- % Done changed from 0 to 90
This task has been largely completed with commit art:78952fc9. What still remains:
- Some interface will have to be introduced that allows a (e.g.) global module to specify the appropriate random-number engine for a given schedule ID.
- Some thought should be given as to how to handle seeding of per-schedule engines, especially if the creation of the multiple engines is hidden from the user.
- Adequate testing has not yet been done to ensure that concurrent engine retrieval from multiple schedules is correctly implemented. It may be hard to test that until parallel schedules are, in-fact, implemented.