Author:
Baranowski Zbigniew,Canali Luca,Fernandez Casani Alvaro,Gallas Elizabeth J,Garcia Montoro Carlos,González de la Hoz Santiago,Hrivnac Julius,Prokoshin Fedor,Rybkine Grigori,Salt Jose,Sanchez Javier,Barberis Dario
Abstract
The ATLAS EventIndex has been in operation since the beginning of
LHC Run 2 in 2015. Like all software projects, its components have been constantly
evolving and improving in performance. The main data store in Hadoop,
based on MapFiles and HBase, can work for the rest of Run 2 but new solutions
are explored for the future. Kudu offers an interesting environment, with a
mixture of BigData and relational database features, which look promising at
the design level. This environment is used to build a prototype to measure the
scaling capabilities as functions of data input rates, total data volumes and data
query and retrieval rates. In this proceedings we report on the selected data
schemas and on the current performance measurements with the Kudu prototype.
Reference9 articles.
1. ATLAS Collaboration,
The ATLAS Experiment at the CERN Large Hadron Collider,
JINST
3
(2008)
S08003
2. The ATLAS EventIndex: architecture, design choices, deployment and first operation experience
Cited by
3 articles.
订阅此论文施引文献
订阅此论文施引文献，注册后可以免费订阅5篇论文的施引文献，订阅后可以查看论文全部施引文献