CPU Resource Table

This page is for the IT internal planning of CPU resources for the LHC experiments, non-LHC experiments and various other groups.

We have now 3 different areas of CPU resource allocations: openstack compute, openstack services and condor batch.

The unit for all CPU processing numbers is HS06.

I am assuming an error bar of about 5% for the presented numbers.

Experiment/Group status Mar 2020 pledge April 2020 pledge April 2021
  [KHS06] [KHS06] [KHS06]
ALICE 350 350 471
ATLAS 411 496 550
CMS 423 423 500
LHCb 86 98 175
         
TOTEM 10 10 12
LHCf 2 2 3
         
ATLAS T3 CERN 7.8 7.8 9.5
CMS T3 CERN 9.4 9.4 12
LHCb T3 CERN 4.8 4.8 6
         
ATLAS T3 Wisconsin 7 3 3
ATLAS T3 Tokyo 9 9 9
         
COMPASS 54 54 68
AMS 155 155 155
Theory 70 70 70
NA48+NA62 50 50 63
NA61 10 10 10
Ship 10 10 10
NP02 7.5 7.5 7.5
NP04 7.5 7.5 7.5
other groups/exp. 50 50 50
         
Sum 1679000   1689000 1689000

UNOSAT,SFT,OPERA,OPAL,L3,ALEPH,DELPHI,NA45,NOMAD,NA38NA50,ITDC,AMSP,etc. have just 4 HS04 in the LSF share

Resources for HPC (e.g. Theory QCD, CFD, BE parallel) are not included in the previous table. Also not included are service resources for IT, EN, GS and BE.

Resource details per experiment

The following table shows the split of the pledges resources across 6 different areas for the 4 LHC experiments. the openstack number are always the quotas and not the used number of cores/HS06

The unit for all CPU processing numbers is [HS06], for openstack the mapping is 1 core = 10 HS06

ALICE

Resource type Apr 2020
  [KHS06]
openstack services 13100
condor 336900
   
total sum 350

ATLAS

Resource type Apr 2020
  [K HS06]
LSF dedicated T0 instance 210000
openstack services 72800
condor 128200
   
total sum 496

CMS

Resource type Apr 2020
  [KHS06]
condor dedicated T0 instance 302000
openstack services 52800
condor 68200
   
total sum 423

LHCb

Resource type Apr 2020
  [KHS06]
openstack services 16000
condor 70000
   
total sum 98

Group codes and experiments

* group_code_mapping.txt: linux group code mappings

Policies

1. The pledged CPU resources for the LHC experiments can be split between the different areas (Voboxes, Shares, dedicated, openstack), but the total pledge is constant.

2. The openstack resources are calculated via the quotas, not the used resources.

History and Changes


Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt group_code_mapping.txt r1 manage 16.3 K 2014-05-18 - 12:55 BerndPanzerSteindel linux group code mappings
Edit | Attach | Watch | Print version | History: r36 < r35 < r34 < r33 < r32 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r35 - 2020-03-17 - BerndPanzerSteindel
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback