1 / 11

WP2 – Grid Application Programming Environment Task 2.2 – MPI Code Debugging and Verification D2.5 - Second Prototype of

WP2 – Grid Application Programming Environment Task 2.2 – MPI Code Debugging and Verification D2.5 - Second Prototype of MARMOT Bettina Krammer, Matthias Müller krammer@hlrs.de , mueller@hlrs.de University of Stuttgart High-Performance Computing-Center Stuttgart (HLRS) www.hlrs.de

niveditha
Download Presentation

WP2 – Grid Application Programming Environment Task 2.2 – MPI Code Debugging and Verification D2.5 - Second Prototype of

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. WP2 – Grid Application Programming EnvironmentTask 2.2 – MPI Code Debugging and VerificationD2.5 - Second Prototype of MARMOT Bettina Krammer, Matthias Müller krammer@hlrs.de, mueller@hlrs.de University of Stuttgart High-Performance Computing-Center Stuttgart (HLRS) www.hlrs.de MARMOT – Second Prototype

  2. Deliverable D2.5 (PM 24) • Documentation of last year‘s work • Documentation of cooperation between different tasks and of integration work MARMOT – Second Prototype

  3. Objectives for next 12 months (Santiago, Feb 2003) • Feedback from users is required • Fortran interface • Use applications from tasks 1.2, 1.3 and 1.4 to test Marmot • Use benchmarks from task 2.3 to test Marmot • Full integration in the Grid environment • Performance measurements and improvements • Supplement documentation and user‘s manual • Dissemination • Debug the debugger in case of bug reports ;-) MARMOT – Second Prototype

  4. Use applications/benchmarks - feedback • Task 1.1 (biomed): • C application • since sunday in cvs • no tests, no feedback • Task 1.2 (flood): • Fortran application • shown in demo yesterday • integration procedure and feedback is a good contribution to D2.5 • Task 1.3 (hep): • ANN (C application) • no issues found by MARMOT MARMOT – Second Prototype

  5. Use applications from WP1/feedback (contd) • Task 1.4 (meteo): • STEMII (Fortran) • Last year, MARMOT detected holes in self-defined datatypes used in MPI_Scatterv/MPI_Gatherv. These holes were removed, which helped to improve the performance of the communication. • Task 2.3 (gridbench): • C/C++/Fortran • No tests so far • Logfiles may be uploaded to MARMOT‘s download area. • Description of tests and extracts of the logfiles will be part of D2.5. • Feedback is welcome. Try to use MARMOT yourselves. MARMOT – Second Prototype

  6. Integration in the Grid environment • Currently, Autobuild is working fine. • MARMOT has proved to run with applications in the testbed. • Integration with Migrating Desktop is going on. • CrossGrid Tutorial: a simple test program named cg-tutorial-marmot-exercise.c containing some erroneous calls can be found in CVS (together with a cg-tutorial-marmot-exercise.jdl). MARMOT – Second Prototype

  7. Performance measurements and improvements • gridbench (task 2.3) was not in cvs last year when we wanted to do our measurements. • MARMOT‘s overhead has been measured using e.g. the ANN-application and some of the NasPB • MARMOT‘s performance has been improved. • Rule of thumb: the higher the ratio of communication/computation, the higher the overhead of MARMOT. MARMOT – Second Prototype

  8. Dissemination/Documentation • Paper submissions to ParCo, Dresden 2003, Journal of Grid Computing (and ICCS, Krakau, june 2004). • Presentation of posters and brochures at several conferences (SC03,...) • Detailed publication list on MARMOT‘s homepage. • Our dissemination activities are reported in standard questionnaires. • Improvement of MARMOT‘s documentation. • D2.5 is a documentation of MARMOT, containing e.g. a user‘s manual, but it‘s only a snapshot. MARMOT‘s README etc. are regularly updated to provide all the information a user needs. MARMOT – Second Prototype

  9. Objectives for next 12 months (Santiago, Feb 2003) • Feedback from users is required still required • Fortran interface done • Use applications from tasks 1.2, 1.3 and 1.4 to test Marmot done • Use benchmarks from task 2.3 to test Marmot not done • Full integration in the Grid environment not fully done • Performance measurements and improvements done • Supplement documentation and user‘s manual done • Dissemination done • Debug the debugger in case of bug reports ;-) done MARMOT – Second Prototype

  10. Further work done • Extended functionality (checks performed on MPI calls) • Improved deadlock detection • Tests on different platforms, using different compilers and MPI implementations, e.g. • IA32/IA64 clusters • IBM Regatta • NEC SX5 • Hitachi SR8000 • Analysis of QA reports: some useful hints, but most issues have very low priority to us. • Preparation of D2.5 document: • first draft done before christmas • draft for internal review not finished yet MARMOT – Second Prototype

  11. Conclusions MARMOT is on track Thanks for your attention MARMOT – Second Prototype

More Related