TRUBA is Turkey's national e-infrastructure that provides computing resources to support research. It began in 2003 with a small cluster and has since expanded significantly. Currently, TRUBA has over 16,000 CPU cores, 3.2 petabytes of storage, and supports over 1800 users across various domains. In the future, TRUBA plans to take on more high performance computing tasks, focus on GPU resources, and play a more active role in European projects like EOSC-hub to further support Turkish researchers.
2. IN THIS PRESENTATION
• A short history
• State of TRUBA resources
• Current trends
• Future plans
3. A SHORT HISTORY
• TR-Grid initiative was established in 2003 and TR-Grid e-
Infrastructure project was supported by TUBITAK funds between
2003-2008
• 2003: 128 CPU linux cluster and testbeds
• 2004: First test sites in SEE-GRID project.
• 2005: TR-Grid CA was accredited.
• 2006-2007: 940 CPU core cluster placed in 6 different geographical areas.
• 2006-2008: EGEE-II, SEE-GRID-II, Eumedgrid
• 2008: 480 CPU core cluster with DDR IB connection and 12TB lustre
filesystem.
4. A SHORT HISTORY
• TR-Grid Research e-Infrastructure Strengthening project was supported by
T.R. Prime Ministry State Planning Organisation (SPO) funds between 2009-
2011.
• 2008-2011: SEE-GRID-SCI, SEERA-EI, EUMedGrid-Support, EGEE-III, EGI-Inspire, e-IRG-SP3, PRACE-
2IP
• 2009: 1216 CPU core cluster in ULAKBIM; 600TB dedicated area for ATLAS and CMS.
• 2010: TR-10-ULAKBIM and TR-03-METU sites were began to serve as Tier-2 Centers of ATLAS and
CMS
• 2010: TR-Grid Infrastructure name was changed to Turkish Science e-Infrastructure – TRUBA by
Scientific Council of Turkish Scientific and Technological Research Center - TUBITAK
• 2010: 5760 CPU core cluster with QDR IB connection and 700TB lustre file system.
• 2011: 4700 CPU core cluster
• Supported VOs: trgrida, trgridb, trgridd, trgride, seegrid, seismo, meteo, env, see, compchem,
biomed, atlas, cms, belle
5. A SHORT HISTORY
• TRUBA Strengthening project is supported by Republic of Turkey Ministry of
Development funds between 2012-...
• 2012-2017: SEERA-EI, EGI-Inspire, e-IRG-SP3, PRACE-2IP, EGI-Engage
• 2012: 32 GPU and 700TB High Available Storage
• 2013: 3072 CPU core cluster in ULAKBIM
• 2014: TR-FC1-ULAKBIM federated cloud site
• 2014: 1024 CPU core cluster and 1.5 Pbyte lustre file system
• 2015: 2 Pbyte lustre file system
• 2017: 4284 CPU core cluster with EDR IB connection.
• 2017: 4800 CPU core cluster, 960 CPU core cluster with 48 Tesla P100 cards and EDR IB
connection.
• Supported VOs: see, biomed, belle, atlas, cms
7. STATE OF TRUBA RESOURCES
CPU cores ≥ 16000
Theoretical TFLOPs ≥ 378
High performance storage capacity 3.2 Pbytes
Registered users ≥ 1800
Computing resource usage ≥ 310 Million CPU core hours
EGI resource usage ≥ 5.3 Million CPU core hours
SCI Publications 454
Theses 104
Supported research projects 50
Supported national communities HEP, Seismology, ELIXIR
Participated EU projects 11
EGI sites 2 Grid, 1 Federated cloud
8. CURRENT TRENDS
• TRUBA’s founding mission is to support long tail of science
• CPU heavy, relatively short and small jobs
• Aimed at researchers to allow new things easily
• TRUBA has also been providing scientific data repositories for
seismology and meteorology communities
• Other data communities also have data repositories under TRUBA
9. CURRENT TRENDS
• There is a need to handle HPC tasks
• No clear undertakers are present now
• TRUBA will also handle HPC tasks
• Meeting HPC requirements will change future expansion and
system design plans
• More emphasis on GPU computing
• Longer jobs with larger resource allocations
10. FUTURE PLANS
• Future direction is toward HPC and tackling bigger problems
• System expansions will also address HPC needs
• Without abandoning the long tail of science
• Support for data repositories will continue
• Continue supporting existing ones
• Add new repositories if needed
11. FUTURE PLANS
• Want to take a more active role in projects
• Interested in using our acquired know-how
• Aiming to start with EOSC-hub
• TRUBA intends to
• Continue supporting current communities, users and repositories
• Dedicate more resources to FC site
• Undertake WPs in EOSC-hub project
