1 / 15

First Prototypes for Grid Application Programming Environment

First Prototypes for Grid Application Programming Environment. Forschungszentrum Karlsruhe GmbH Hauptabteilung Informations- und Kommunikationstechnik Hermann-von-Helmholtz-Platz 1 D-76344 Eggenstein-Leopoldshafen Holger Marten http://grid.fzk.de.

ludlow
Download Presentation

First Prototypes for Grid Application Programming Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. First Prototypes for Grid Application Programming Environment Forschungszentrum Karlsruhe GmbH Hauptabteilung Informations- und Kommunikationstechnik Hermann-von-Helmholtz-Platz 1 D-76344 Eggenstein-Leopoldshafen Holger Marten http://grid.fzk.de

  2. CrossGrid WP2 – Grid Application Programming Environment • Task 2.2 MPI code debugging & verification tool •  verify parallel, distributed MPI applications on Grid • Task 2.3 Metrics & Benchmarks •  describe performance of Grid applications & Grid configurations • Task 2.4.1 Interactive & semiautomatic performance evaluation • measure, evaluate, visualize performance of Grid applications (W. Funika) • Task 2.4.2 Interactive & semiautomatic performance evaluation • predict performance of Grid applications (F.F. Rivera)

  3. WP2 – Done so far PM 01-03 Software Requirement Specifications (SRS) = D2.1 - four documents PM 04-06 Design and interfaces of the tools (DES) = D2.2 - five documents PM 07-12 Write first prototypes PM 10-12 First (WP2 internal) integration, testing, refinement = D2.3 - five documents (January 18, 2003) part I: Prototypes Summary part II: MARMOT part III: GridBench part IV: G-PM, Grid-enabled Performance Measurement part V: PPC, Performance Prediction Component

  4. First prototypes: Task 2.2 – MARMOT (MPI) Goal: verify parallel, distributed MPI applications on Grid

  5. First prototypes: Task 2.2 – MARMOT (MPI) • Status & available functionalities • library with MPI calls used by WP1 applications • environment variables for tool behaviour and output • output = errors, warnings, notes; human readable • test programs provided • available in CVS • installed & tested with HEP application (Task 1.3) on UI of CSIC testbed • WP4 integration support by Jesus Marco, CSIC • first revision of D2.3 part II available • installation on CESGA development workstation completed yesterday

  6. 1st prototype First prototypes: Task 2.3 – GridBench Goal: Benchmark applications and Grid configurations on different levels of refinement Grid site CE/SE micro kernels application kernels micro benchmarks

  7. First prototypes: Task 2.3 – GridBench • Status & available functionalities • kind of “MPI application” based on High Performance LINPACK • restricted to run on single local testbeds • restricted to data after completion (no data at runtime) • measures FLOP/s of LINPACK problems • input & output are XML files • available in CVS • installed & tested on CE of UCY testbed • installation on UI of AUTh finished yesterday • WP4 integration support by Christos Kanellopoulos, AUTh • installation & rpm on CESGA development workstation in progress

  8. First prototypes: Task 2.4.1 – G-PM Goal: Online measurement & visualisation of Grid application performance API API Task 3.3

  9. First prototypes: Task 2.4.1 – G-PM • Status & available functionalities • all components available, prototype with limited functionality • restricted to run on a local Linux workstation • connected with OCM-G on same site; • application instrumentation in OCM-G available • available in CVS • installed & tested on UI of CYFRONET testbed • WP4 integration support by Piotr Nyczyk, CYFRONET • installation & rpm on CESGA development workstation in progress • will be tested with HEP application of Task 1.3

  10. First prototypes: Task 2.4.2 – PPC Goal: predict application performance on Grids Monitoring Task 3.3 WP1 kernels (vertlq,...) Analytical prediction model Benchmarks Matrix-vector product Iterative solvers... Kernel Graphical User Interface (TCL/TK, PlPlot) Change grid info USER PPC results

  11. First prototypes: Task 2.4.2 – PPC • Status & available functionalities • restricted number of implemented kernels: matrix-vector product, • sparse matrix solvers, verteql of T1.4 (air polution) • GUI restricted to matrix-vector product & sparse matrix solvers • restricted to simulate homogeneous systems (non-Grid) • source code of kernels provided • available in CVS • installed & tested on UI of U.S.C. testbed • WP4 integration support by Carlos Fernandez, CESGA • installation on CESGA development workstation done

  12. Summary of 1st prototype status status 09-02-2003 18:30

  13. Discussion Matrix I • Tuesday, Feb 11, 15:00-16:30, this room?? • Meeting all WPs • review of integration achievements • GridBench & PPC need WP1 kernels • who will test our tools ? • Tuesday, Feb 11, 17:00-17:45, Seminario 2, 45 mins enough? • WP2 meets Task 3.1 • portals for GridBench, G-PM & PPC • Tuesday, Feb 11, 17:45-18:30, Seminario 2 • WP2 meets Task 3.3 • interfaces of GridBench & G-PM to OCM-G • use of R-GMA by GridBench

  14. Discussion Matrix II • Wednesday, Feb 12, 9:00-10:30, Seminario 2 • WP2 internal • plans for yearly review • plans for next year • how to create a real environment • GridBench needs API from G-PM • checking GridBench with MARMOT ? • Wednesday, Feb 12, ??, room ?? • Task 2.4.2 already met Task 3.3.1-3.3.4 yesterday • Grid Monitoring Tasks will deliver input for PPC • Wish to meet WP1: “flooding”, “weather forecast”, “air polution”

  15. Issues during last weeks • Timing • D2.3 due on 18/01/2003 = 4-6 weeks ahead of original plan • D2.3 delivered on 18/01/2003; not yet received review reports • results of testing & installation were planned as part of D2.3 • Tools • vision was “one environment, common look & feel”; now 4 separate tools • tools were planned to be installed on one test site (FZK) • installation; what does it mean ??  Things converged during the last days integration meetings Thanks to WP2 members and the Integration Team.

More Related