270 likes | 382 Views
WP9 (Future Technologies) 1 st Internal GRNET meeting . Ioannis Liabotis ( iliaboti@grnet.gr ) 07 Oct 2010. Overview. General PRACE and PRACE-1IP Info WP9 Description & WP9 tasks for GRNET Internal Organization DefineAction points. PRACE Who is Who (2/2). … PRACE AISBL
E N D
WP9 (Future Technologies) 1st Internal GRNET meeting IoannisLiabotis (iliaboti@grnet.gr) 07 Oct 2010
Overview • General PRACE and PRACE-1IP Info • WP9 Description & WP9 tasks for GRNET • Internal Organization • DefineAction points
PRACE Who is Who (2/2) • … PRACE AISBL • Will provide Tier-0 resources worth 400 … 500 Mio € in the next 5 years • Has limited funding for related activities(600 k€ membership fees in 2010) • PRACE-1IP (July 2010 – June 2012) • EC-funded project to support and accelerate the implementation of the Tier-0 Infrastructure • “Beneficiaries” are all members of the AISBL • Mandate to represent a country in HPC on the European level • Involve other national HPC competencies and resources as Third Parties • PRACE-2IP Proposal (mid 2011 – mid 2013 ?) • Will integrate the national “DEISA-type” HPC resources and services • Will provide user community support, technology assessment, training, …
PRACE – A Partnership with a Vision • Provide world-class HPC systems for word-class science • Support Europe in attaining global leadership in public and private research and development • Create a world-leading persistent high-end HPC infrastructure managed as a single legal entity • Deploy systems of the highest performance level (Tier-0) • Ensure a diversity of architectures to meet the needs of European user communities • Collaborate with vendors and ISVs on strategic HPC technologies • Provide support and training … and a Mission
PRACE-1IP Structure & Objectives (1/2) • WP1: Management of the Contract • WP2: Evolution of the Research Infrastructure • Provide advice for the legal, administrative and financial processes of the AISBL • WP3: Dissemination and Training • Provide advanced HPC training and a training portal • Promote the PRACE brand in international events • WP4: HPC Ecosystem Relations • Integrate PRACE in the European HPC ecosystem • WP5: Industrial User Relations • Address the specific requirements of European industry
PRACE-1IP Structure & Objectives (2/2) • WP6: Technical Operation and Evolution of the Distributed Infrastructure • Manage and support the distributed systems and diverse architectures consistently • WP7: Enabling Petascale Applications: Efficient Use of Tier-0 Systems • Port, petascale and optimise applications for the Tier-0 systems as a service for the users of the PRACE RI • WP8: Support for the Procurement and Commissioning of HPC Service • Maintain the close relation with HPC vendors and advise the PRACE RI on future procurements • WP9: Future Technologies • Assess advanced architectures to foster European developments towards future multi-Petaflop/s systems • Assume a driving role in the international exascale collaborations
Inconsistencies are due to the fact that the PM per task are taken from an outdated table, the “Total WP9” figures should be correct.
T9.1 „Technology Watch & Assessment“ Lead: Jonathan Follows, STFC • T9.1 topics according to DoW: • Processing units with many cores, possibly heterogeneous • Novel memory technologies (e.g., 3D stacked memory, Spin Torque Transfer • Magnetic RAM, Ferroelectric Random Access Memory (FRAM) or Molecular memory) • I/O issues, mass storage and file system technologies • Optical Interconnects and optimized network routing algorithms in very large HPC networks • Power supply and cooling • System software and tools T9.2 <- Possible GRNET contribution here • Programming languages and paradigms T9.2 <- Possible GRNET contribution here
T9.1 continued … • Workshop on energy-efficient emergent component technologies, 18.-20. Oct, Amsterdam (organized by Aad van der Steen): • Processora: ARM, Adapteva, Intel, ST Microelectronics, SDS, Tilera • FPGA/DSP related HW: Altera, Xilinx • FPGA/DSP related SW: PetaPath, ZigTaq • Memory: HP (memristors), MRAM (Crocus), PRAM (Micron (Numonyx)) • Opt. Networks: Optical netw. (HP), Optical netw. (IBM), Optical netw. (Columbia U)
T9.2 „Multi-Petascale Software Environment“Lead: Volker Strumpen, JKU • Topics according to DoW;Task and Work distribution • ST 9.2.A „Programming Languages“ (Iris Christadler, LRZ) <-GRNET involvement here • ST 9.2.B „Tools, Perf. Analysis & Monitoring“ (Jesus Labarta, BSC) <-GRNET Involvement here • ST 9.2.C „System Management“ (Jacques-Charles, CEA) • ST 9.2.D „GPGPUs & Accelerators“ (Guillaume Colin de Verdiere, CEA) Name and Subtask-leadership of ST 9.2.D have been finalized during a meeting on Tuesday, Aug 31. (See next slide.)
Collection of possible content for the subtask ST 9.2.D GPGPU & Accelerators • Mathematical kernels on 1 GPU, multiple GPUs“Which kind of codes will be able to benefit from GPUs?” “Will this change in the future, e.g. with direct connections between GPUs?” • Cluster GPGPU: “How to make GPU computing scale?” • Communication GPU-CPU, GPU-GPU • Portability and Performance • Programming models for GPUs (CUDA, OpenCL, CAPS, PGI,+MPI) • Energy-efficiency of GPUs (together with T9.3) • Hybrid solutions (e.g. Fusion for HPC), programming solutions for hybrid architectures • FPGAs, new programmability approaches • Evtl. final evaluation of the Clearspeed prototype • “Single-chip Cloud Computer ”, Knights Ferry, … Results of the meeting on Tuesday morning. Input from SadafAlam (CSCS), Guillaume Colin de Verdiere (CEA), RadekJanuszewski,(PSNC), Iris and Herbert.
T9.3 „Future Highly Energy Efficient Tier-0 Systems“Lead: LennartJohnsson, SNIC • Topics according to DoW • Additional research using the prototypes purchased in the PRACE Preparatory Phase project • Immediately start process to select, deploy and evaluate prototypes (components or systems) • Assess, and make recommendations to the RI for joint developments with industrial partners to develop highly energy efficient HPC components and systems, as well as power and cooling technologies. • Propose future highly energy efficient multi-Petascale system architectures, and identify technologies for improving energy efficiency of future supercomputing centre design.
Deliverables (orderedbytask) • D9.1.1 Multi-Petascale technologyassessmentreport: [M12, RE] <-<- GRNET contribution hereReport on future multi-Petascale technologies (2012-2014) • D9.1.2 Exascaletechnologyassessmentreport [M21, RE] <- GRNET contribution hereReport on future multi-PetatoExascaletechnologies (2014-2018) • D9.2.1 First report on multi-Peta- to Exascale software [M10, PU] <- GRNET contribution hereReport on promising novel HPC software solutions • D9.2.2 Final software evaluation report [M22, PU] <-GRNET contribution hereProposal for software solutions to be used in future European systems • D9.3.1 Proposal for additional prototypes [M4, RE]Based on this report a set of prototypes will be selected for evaluation • D9.3.2 Report on prototypes selection [M8, RE]Report on the prototype selection process and result • D9.3.3 Report on prototypes evaluation [M24, PU]Assessment of technologies and system designs from an energy efficiency perspective; including a proposal for a next generation of European multi-Petascale architectures and desirable directions for future HPC R&D.
Deliverables(bydate, plannedcontent, year1) • D9.3.1 Proposal for additional prototypes [M4, RE]Mind-map from WP8 F2F, Prototype selection process, “coarse-grain” prototype proposals • D9.3.2 Report on prototypes selection [M8, RE]Report on selection process & results: Prototype selection process, minutes from WP9 F2F 20.Oct (refinement of proposals), “fine-grain” proposals, voting results, TB decision, MB decision • D9.2.1 First report on multi-Peta- to Exascale software [M10, PU]Justification for the selection of research topics, first results from the assessment of languages, tools, accelerators, etc., roughly one chapter per T9.2 subtask • D9.1.1 Multi-Petascaletechnologyassessmentreport: [M12, RE]Technology timeframe 2012-2014, collectionofvendorpresentations (simplyputpdfstogether), short (max 20 pages) „highlights“ fromthevendormeetings, comparisonofroadmaps, etc.
Deliverables(bydate, plannedcontent, year2) • D9.1.2 Exascaletechnologyassessmentreport [M21, RE]Technology timeframe 2014-2018, otherwisesee D9.1.1 • D9.2.2 Final software evaluation report [M22, PU]Proposal for software solutions to be used in future European systems: final results from all T9.2 subtasks, results should be published as (white) papers, mainly a collection of “highlights”/”comparisons”/”links to papers” • D9.3.3 Report on prototypes evaluation [M24, PU]Report of all prototypes & prototype results, main results for each prototype should be published in (white) papers, deliverable “highlights” results and tries to compare technology were possible and sensible.
Prototype Selection Proc. (Overview) • Coarse-grain proposals for prototypes. (Sep 6-16) • Classification and presentation of proposals. (TC) • Discussion and adaptation of proposals. (F2F, Oct 20) • Fine-grained proposals. (Nov 1-30) • Voting & Selection. (Beginning of Dec) • MB decision. (Dec)
Prototype SelectionProcess (slide 1/4) • Coarse-grain proposals for prototypes.Collaborative proposals are not necessary (step 3). Proposals could be withdrawn anytime in the process before step 6. Max 3 pages: “Key objectives”, basic description, “Hardware”, “Energy-efficiency” & “Software”.“Impact for Exascale Computing”.“Collaborations, experiences and preparatory work”, scientific communities/codes/applications that will benefit. • Classification and presentation of proposals. Rough (technical) classification . Presentations by proposer during WP9 F2F meeting (Oct 20).
Prototype SelectionProcess (slide 2/4) • Discussion and adaptation of proposals. (during Oct 20 F2F Mtg). • Possible adaptations: • Dismiss proposals that are not compliant with WP9 goals. • Combine proposals to investigate several aspects of a particular prototype (e.g. energy efficiency and programmability of certain hardware). • Combine proposals of similar nature. • Add small contributions from other partners to good proposals. • Adjust amount of funding necessary for each prototype proposals. • Try to narrow the field down to 3-5 prototypes.
Prototype SelectionProcess (slide 3/4) • Fine-grained proposals for the agreed prototypes.Proposals are typically handed in by a consortium of partners. Proposals do not exceed 10 pages. They contain: • High-level overview of the prototype. • Detailed description of the prototype and the associated assessment. • Impact of the prototype on Exascale computing, software, energy efficiency, scientific communities/codes/applications and/or hardware development. • Detailed timeline for the assessment. • Break-down of tasks between partners. • Costs & requested funding (including the distribution between partners).
Prototype SelectionProcess (slide 4/4) • Voting & Selection. Each WP9 partner site can vote for 3 prototypes >> “priority list” >> granted as long as funding is available. • Decision. TB prepares a MB proposal based on WP9 information. MB takes the decision. Please see https://bscw.zam.kfa-juelich.de/bscw/bscw.cgi/427518 for an update on the prototype selection process taking into account the recommendations from the TB and WP9 F2F.
Important dates 3.Sep: MB Mtg (Decision on Prototype Selec. Process) 6.Sep-16.Sep: Preparation of coarse grain proposals 16.Sep-10.Okt. Preparation of M4 Deliverable D9.3.1 „Proposal for additional prototypes“ (classification of proposals, all coarse grain proposals will be added to the annex) 24.Sept.: WP9 TelCon 18.-20. Oct. Workshop on energy efficient emergent component technologies, Amsterdam 20.Oct: One-day WP9 F2F, (Amsterdam), discussion & adaptation of proposals <- Who goes there? (1 person) 1.-30 Nov: Submission of fine-grain proposals End Nov/Dec: STRATOS Mtg 6.Dec: WP9 TC, discussion of proposals, clarifications 10.Dec: Deadline email-votes WP9 partners Mid/End Dec: TB and MB decision to meet M6 milestone MS91 „Promising architectures and component development projects selected“
Internal Organization • Names and mail addresses needed to be included in the PRACE-1IP mailing lists • Internal mailing list: prace-1ip-wp9-gr@lists.grnet.gr • Names and e-mail addresses needed • http://code.grnet.gr/projects/prace-npt - Project created for tasks registration, code and documents uploading • Organise internal f2f meetings like this one
Action Points • Fix communication and collaboration tools – see previous slide • Decide on task commitments • We need an evaluation of the new programming models defined in proposal – 1 page evaluation each • Types of problems they are suitable for • License issues • Possible Interest by the Greek community • Prototype Evaluation: You can make your suggestions with some justification • Report and presentation from 1st f2f meeting