cet::Ntuple, which is not yet thread safe. The
TimeTracker service would need to be thread aware for calculating time differences, which are then inserted into the database. We should investigate if using CMSSW's
StallMonitor, and suitably adjusting it to use SQLite, could be of benefit.
#3 Updated by Kyle Knoepfel almost 4 years ago
- Status changed from Assigned to Resolved
- % Done changed from 40 to 100
Thread-safety achieved by representing time point data as an
std::vector<PerScheduleData>, where the vector grows to the number of schedules specified by the user. Right now, there is a placeholder number of 1 schedule, which can be replaced by the necessary facility that communicates how many schedules have been configured by the user.
Implemented with commit art:f4d403e7.