Abstract
The Resource Manager is one of the core components of the Data Acquisition system of the ATLAS experiment at the LHC. The Resource Manager marshals the right for applications to access resources which may exist in multiple but limited copies, in order to avoid conflicts due to program faults or operator errors. The access to resources is managed in a manner similar to what a lock manager would do in other software systems. All the available resources and their association to software processes are described in the Data Acquisition configuration database. The Resource Manager is queried about the availability of resources every time an application needs to be started. The Resource Manager’s design is based on a client-server model, hence it consists of two components: the Resource Manager “server” application and the “client” shared library. The Resource Manager server implements all the needed functionalities, while the Resource Manager client library provides remote access to the “server” (i.e., to allocate and free resources, to query about the status of resources). During the LHC’s Long Shutdown period, the Resource Manager’s requirements have been reviewed at the light of the experience gained during the LHC’s Run 1. As a consequence, the Resource Manager has undergone a full re-design and re-implementation cycle with the result of a reduction of the code base by 40% with respect to the previous implementation. This contribution will focus on the way the design and the implementation of the Resource Manager could leverage the new features available in the C++11 standard, and how the introduction of external libraries (like Boost multi-container) led to a more maintainable system. Additionally, particular attention will be given to the technical solutions adopted to ensure the Resource Manager could effort the typical requests rates of the Data Acquisition system, which is about 30000 requests in a time window of few seconds coming from more than 1000 clients.
Highlights
IntroductionThe Trigger and Data Acquisition[1](TDAQ) system of the ATLAS[2] detector at the Large Hadron Collider (LHC) at CERN is composed of a large number of distributed hardware and software components (about 3000 machines and more than 15000 concurrent processes at the end of LHC’s Run I) which provide the data-taking functionality of the overall system
The Trigger and Data Acquisition[1](TDAQ) system of the ATLAS[2] detector at the Large Hadron Collider (LHC) at CERN is composed of a large number of distributed hardware and software components which provide the data-taking functionality of the overall system.The Resource Manager (RM) is one of the core components of the ATLAS online Data Acquisition system
All the available resources that are used by the RM and their associations to software processes are described in the configuration database
Summary
The Trigger and Data Acquisition[1](TDAQ) system of the ATLAS[2] detector at the Large Hadron Collider (LHC) at CERN is composed of a large number of distributed hardware and software components (about 3000 machines and more than 15000 concurrent processes at the end of LHC’s Run I) which provide the data-taking functionality of the overall system. The Resource Manager (RM) is one of the core components of the ATLAS online Data Acquisition system. The Resource Manager marshals the right for applications to access resources which may exist in multiple but limited copies in order to avoid conflicts due to program faults or operator errors. The Resource Manager is queried about the availability of resources every time any application needs to be started. During routine ATLAS operations many applications must be started and stopped within a small time window. The Resource Manager is designed to handle of order 30k requests within a few seconds from O(1k) clients in the data acquisition system via a custom API. A GUI is available for use by experts to view and update resources as needed
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.