Implementing Concurrent Non-Event Transitionsin CMS

Abstract

Available on CMS information serverCMS CR -2018/277The Compact Muon Solenoid ExperimentMailing address: CMS CERN, CH-1211 GENEVA 23, SwitzerlandConference Report15 October 2018 (v2, 21 November 2018)Implementing Concurrent Non-Event Transitionsin CMSChristopher Jones for the CMS CollaborationAbstractSince the beginning of the LHC Run 2 in 2016 the CMS data processing framework, CMSSW, hasbeen running with multiple threads during production of data and simulation via the use of IntelsThread Building Blocks (TBB) library. The TBB library utilizes tasks as concurrent units of work.CMS used these tasks to allow both concurrent processing of events as well as concurrent running ofmodules processing the same event. This design has served CMS well and has allowed jobs to utilizeless memory per core as well as reduce the number of jobs that must be tracked by CMSs worflowmanagement system. As CMS has begun to utilize greater number of threads in a job, the effect ofserialization points in the framework has decreased jobs CPU efficiency. One major serialization pointoccurs when the framework processes a non-Event transition. These transitions occur when a new Runor LuminosityBlock is to be processed. In this talk we will discuss how the different transitions definethe processing model for CMSSW and how we were able to successfully allow concurrent process-ing of those transitions using TBB via task queues. We will also show CPU efficiency comparisonsbetween the same work being done with and without the additional concurrency.