M. Lautenschlager (M&D) / / 1 ENES: The European Earth System GRID ENES – Alcatel WS , ANTWERPEN Michael Lautenschlager Model and Data Max-Planck Institute for Meteorology Hamburg Mail: / Web:

M. Lautenschlager (M&D) / / 2 ENES GRID Successful modelling and prediction of the Earth System relies heavily on the availability of huge data sets for boundary and initial conditions from observations and other model studies, and on comparison with the output of other model studies. Networking Aspects: NRN cooperation, bandwidth, latency, quality of service, middleware integration Software Aspects: science supporting data processing and visualisation, data and metadata standards, authorising systems Data Archives: standardisation of data models, primary data and meta data organization, long-term storage, data quality, data access Organizational Aspects: load balancing, job scheduling, trans- national access, rights management, cost management

M. Lautenschlager (M&D) / / 3 Model Computing GRID (PRISM) + distributed computing

M. Lautenschlager (M&D) / / 4 Data Processing GRID + processing

M. Lautenschlager (M&D) / / 5 ENES Partners

M. Lautenschlager (M&D) / / 6 Traffic Matrix DKRZ (G) Archive: 3.5 Tbytes/day Restore: 1.5 Tbytes/day Total: 600 Tbytes Hadley Centre (GB) Archive: 250 Gbytes/day Restore: 400 Gbytes/day Total: 200 Tbytes Mass Storage Archives Extrapolation of data rates depends on installed compute power and application profiles (comp. Use Cases) IPSL (F) Archive: 170 Gbytes/day Restore: 330 Gbytes/day

M. Lautenschlager (M&D) / / 7 Traffic Matrix: Questions  What is the minimum, guaranteed bandwidth?  What is the average bandwidth?  What is the peak bandwidth?  What are the quality requirements especially latency?

M. Lautenschlager (M&D) / / 8 Traffic Matrix: Alcatel - Questionaire  Server included DKRZ: Sun-Solaris and Linux (Suse + Red Hat) for data, NEC SX6 for computing Hadley: IBM Z-series for data, NEC + Cray T3E for computing, HP UX server for web IPSL: NEC SX5, IBM SP4, Fujitsui VPP, Compaq for computing, SGI for data  Protocols DKRZ: TCP/IP Hadley: TCP/IP IPSL: TCP/IP

M. Lautenschlager (M&D) / / 9  Services DKRZ: External: Apache, proftp, OpenSSH, SMTP, cvs, Oracle Appl.Server + DB-Server, Open DAP Internal: LDAP, NIS, NFS, CUPS Hadley: very similar IPSL: very similar, Open DAP  Client Systems DKRZ: Sun-Solaris, Windows 2000, Linux, (Mac) Hadley: Linux, HP-UX Windows XP IPSL: Sun-Solaris, Windows 2000, Linux, Mac Traffic Matrix: Alcatel - Questionaire

M. Lautenschlager (M&D) / / 10  Applications for ENES Model development Run coupled climate models Process and analyse climate model data Process and analyse observations  Future DKRZ: We plan for a European Climate Computing Facility because our analysis so far shows that distributed computing is not an option for single model components (needs further investigation). Hadley: Future grid applications will include tools for finding, navigating and extracting subsets of model and observation datasets. Also possibly tools for model intercomparison and running ensembles of different models. Traffic Matrix: Alcatel - Questionaire

M. Lautenschlager (M&D) / / 11 Future Development Path Internet Access DB Access HSM Access

M. Lautenschlager (M&D) / / 12 (IV/2001) January 2003: 600 TB

M. Lautenschlager (M&D) / / 13 CERA-DB Access

M. Lautenschlager (M&D) / / 14 CERA DB Access  Number of Downloads in 2002: 2000 – 5000 / month 80% are external  Total Data Volume: 100 – 400 GB / month  Data per Download: 50 – 100 MB Current database size is Terabyte Number of experiments: 288 Number of datasets: Number of blob within cera at 28-JAN-03:

M. Lautenschlager (M&D) / / 15 FTP-Access to UniTree-System Up to > Read : Write = 2 : 1 for climate datasets Data rates January 2003: 1.5 TB/day Read 3.5 TB/day Write

M. Lautenschlager (M&D) / / 16 DKRZ-Internet: G-WiN Received by DKRZ Sent by DKRZ

M. Lautenschlager (M&D) / / 17 Statistik ERA40 Daten ===================== load size | | | | Mon. MB start end diff rate start end diff rate : :15 09:08=188MB/h 23-08: :37 :35=2.9GB/h : :49 07:34=205MB/h 23-10: :05 :30=3.1GB/h : :30 09:41=178MB/h 23-16: :09 :35=2.9GB/h : :30 10:00=166MB/h 24-11: :31 :31=3.1GB/h : :16 07:46=221MB/h 24-12: :14 :35=2.9GB/h : :10 12:56=129MB/h 24-23: :54 :32=3.0GB/h : :15 11:05=155MB/h 25-12: :17 :37=2.8GB/h : :34 09:19=185MB/h 25-23: :24 :36=2.9GB/h : :49 07:15=230MB/h 26-10: :48 :37=2.8GB/h : :21 06:32=263MB/h 26-10: :51 :39=2.7GB/h : :31 06:10=270MB/h 26-20: :16 :34=3.0GB/h : :01 05:30=313MB/h 26-20: :19 :36=2.9GB/h Example WAN Data Transfer File Size Retrieval Rate Transfer Rate

M. Lautenschlager (M&D) / / 18 ERA40 - Data Transfer: ECMWF  DKRZ Data extraction from ECMWF Archive (Retrieval):  daily average 200 MB/h (single request)  day time 170 MB/h,  night time and week end 300 MB/h FTP download (Transfer):  1 GB in 20 minutes per transfer process,  also 1 GB / 20 min / transfer for two parallel FTP's

M. Lautenschlager (M&D) / / 19 UC: Uses Cases 2D / 3D time series Raw data transfer Blending of different data sources

M. Lautenschlager (M&D) / / 20 Standard Model Resolution Number of horizontal grid points for entire globe T42: 64 x 128 points (present) T63: 96 x 192 points (next) T106: 160 x 320 points (future)

M. Lautenschlager (M&D) / / 21 UC: Transfer Data Volume and Response Time Requirements  Basic application: time series access (TS) 2D and 3D TS from 500 model years as monthly means (MM), response time of 5 sec 2D and 3D TS from 100 model years with 6 hours storage interval (6H), response time of 10 sec Raw data TS output from 50 model years, response time of 20 sec  Model configurations T42-L19: 17.5 KB/global-field, 0.4 GB/model-month T63-L31: 37.5 KB/global-field, 1.5 GB/model-month T106-L31: KB/global-field, 5.6 GB/model-month

M. Lautenschlager (M&D) / / 22 DT: Time Series and Data Transfer Volume TSLengthT42-L19T63-L31T106-L31 2D (MM)500 Y D (MM)500 Y2718 2D (6H)100 Y3514 3D (6H)100 Y Raw50 Y Units: GB (Table entries are rounded.)

M. Lautenschlager (M&D) / / 23 DT: Response Time and Net Band Width on Application Level TS Response Time T42-L19T63-L31T106-L31 2D (MM)5 sec D (MM)5 sec D (6H)10 sec2410 3D (6H)10 sec Raw20 sec Units: Gbit/sec (Table entries are rounded.) ERA40: Gbit/sec

M. Lautenschlager (M&D) / / 24 Traffic Matrix: Working Hypothesis  Dynamic infrastructure which takes into account changing distribution of "hot spots" and flexible adaptation to applications. Layer 1: Hot Spots (peak = 1.4 Tbit/s) ECMWF, Exeter, Hamburg, France, Poland?, Scandinavia?, Italy? (Users/Producers) Layer 2: ENES Partners + e.g. Earth Simulator Community, Earth System Grid,.... (30% of peak) MPI-M, NERSC, IPSL, DMI, KNMI, CGAM, Meteo-France, CERFACS, CSCS, SMHI, UCL, INGV, MPI-BGC, IfM Kiel, CRU-UEA, FZJ, ICMCM, Hamburg University, AWI, IfM-Berlin, ZIB Layer 3: Rest of the World (5% of peak)  What is the minimum, guaranteed bandwidth? 10 % of peak(1,2,3)  What is the average bandwidth? 50% of peak(1,2,3)  What is the peak bandwidth? Peak(1,2,3) for 10% of day