Abstract
LHCb has been using the CERN/IT developed Conditions Database library COOL for several years, during LHC Run 1 and Run 2. With the opportunity window of the second long shutdown of LHC, in preparation for Run 3 and the upgraded LHCb detector, we decided to investigate alternatives to COOL as Conditions Database backend. In particular, given our conditions and detector description data model, we investigated the possibility of reusing the internal Git repository database as a conditions storage, and we adopted it since 2017 data taking. The adoption of Git gave us improved performance, smaller storage size and simplified maintenance and deployment.
In this paper we describe the implementation of our Git Conditions Database and the way it simplified our detector description and conditions development workflow.
Reference8 articles.
1. Valassi A.,
Basset R.,
Clemencic M.,
Pucciani G.,
Schmidt S.A.,
Wache M.,
COOL, LCG conditions database for the LHC experiments: Development and deployment status, Proceedings,
2008 IEEE Nuclear Science Symposium, Medical Imaging Conference and 16th International Workshop on Room-Temperature Semiconductor X-Ray and Gamma-Ray Detectors
(NSS/MIC 2008 / RTSD 2008) :
Dresden, Germany,
October 19-25, 2008
pp. 3021–3028
(2008)
2. SQLite project,
SQLite,
[software],
https://sqlite.org,
[accessed 2018–10–27]
3. Chytracek R.,
Düllmann D.,
Govi G.,
Kalkhof A.,
Molnár Z.,
Valassi A.,
Distributed database access in the LHC computing grid with CORAL,
pp. 3029–3035
(2008)
4. Distributing LHC application software and conditions databases using the CernVM file system
5. Git project,
Git Distributed Version Control System,
[software],
https://git-scm.com/,
[accessed 2018–10–27]