CMS conditions data access using FroNTier
Abstract
The CMS experiment at the LHC has established an infrastructure using the FroNTier framework to deliver conditions (i.e. calibration, alignment, etc.) data to processing clients worldwide. FroNTier is a simple web service approach providing client HTTP access to a central database service. The system for CMS has been developed to work with POOL which provides object relational mapping between the C++ clients and various database technologies. Because of the read only nature of the data, Squid proxy caching servers are maintained near clients and these caches provide high performance data access. Several features have been developed to make the system meet the needs of CMS including careful attention to cache coherency with the central database, and low latency loading required for the operation of the online High Level Trigger. The ease of deployment, stability of operation, and high performance make the FroNTier approach well suited to the GRID environment being used for CMS offline, as well as for the online environment used by the CMS High Level Trigger (HLT). The use of standard software, such as Squid and various monitoring tools, make the system reliable, highly configurable and easily maintained. We describe the architecture, software, deployment, performance, monitoring and overallmore »
- Authors:
- Publication Date:
- Research Org.:
- Fermi National Accelerator Lab. (FNAL), Batavia, IL (United States)
- Sponsoring Org.:
- USDOE
- OSTI Identifier:
- 922731
- Report Number(s):
- FERMILAB-CONF-07-526-CD
TRN: US0801744
- DOE Contract Number:
- AC02-07CH11359
- Resource Type:
- Conference
- Resource Relation:
- Conference: Prepared for International Conference on Computing in High Energy and Nuclear Physics (CHEP 07), Victoria, BC, Canada, 2-7 Sep 2007
- Country of Publication:
- United States
- Language:
- English
- Subject:
- 99 GENERAL AND MISCELLANEOUS//MATHEMATICS, COMPUTING, AND INFORMATION SCIENCE; ALIGNMENT; ARCHITECTURE; CALIBRATION; MONITORING; NUCLEAR PHYSICS; PERFORMANCE; PROCESSING; STABILITY; Computing
Citation Formats
Blumenfeld, Barry J., /Johns Hopkins U., Dykstra, David, Lueking, Lee, Wicklund, Eric, and /Fermilab. CMS conditions data access using FroNTier. United States: N. p., 2007.
Web.
Blumenfeld, Barry J., /Johns Hopkins U., Dykstra, David, Lueking, Lee, Wicklund, Eric, & /Fermilab. CMS conditions data access using FroNTier. United States.
Blumenfeld, Barry J., /Johns Hopkins U., Dykstra, David, Lueking, Lee, Wicklund, Eric, and /Fermilab. Mon .
"CMS conditions data access using FroNTier". United States. https://www.osti.gov/servlets/purl/922731.
@article{osti_922731,
title = {CMS conditions data access using FroNTier},
author = {Blumenfeld, Barry J. and /Johns Hopkins U. and Dykstra, David and Lueking, Lee and Wicklund, Eric and /Fermilab},
abstractNote = {The CMS experiment at the LHC has established an infrastructure using the FroNTier framework to deliver conditions (i.e. calibration, alignment, etc.) data to processing clients worldwide. FroNTier is a simple web service approach providing client HTTP access to a central database service. The system for CMS has been developed to work with POOL which provides object relational mapping between the C++ clients and various database technologies. Because of the read only nature of the data, Squid proxy caching servers are maintained near clients and these caches provide high performance data access. Several features have been developed to make the system meet the needs of CMS including careful attention to cache coherency with the central database, and low latency loading required for the operation of the online High Level Trigger. The ease of deployment, stability of operation, and high performance make the FroNTier approach well suited to the GRID environment being used for CMS offline, as well as for the online environment used by the CMS High Level Trigger (HLT). The use of standard software, such as Squid and various monitoring tools, make the system reliable, highly configurable and easily maintained. We describe the architecture, software, deployment, performance, monitoring and overall operational experience for the system.},
doi = {},
journal = {},
number = ,
volume = ,
place = {United States},
year = {Mon Oct 01 00:00:00 EDT 2007},
month = {Mon Oct 01 00:00:00 EDT 2007}
}