1 / 25

HYDRA: Using Windows Desktop Systems in Distributed Parallel Computing

HYDRA: Using Windows Desktop Systems in Distributed Parallel Computing. Arvind Gopu, Douglas Grover, David Hart, Richard Repasky, Joseph Rinkovsky, Steve Simms, Adam Sweeny, Peng Wang University Information Technology Services Indiana University. Problem Description.

maxim
Download Presentation

HYDRA: Using Windows Desktop Systems in Distributed Parallel Computing

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. HYDRA: Using Windows Desktop Systems in Distributed Parallel Computing Arvind Gopu, Douglas Grover, David Hart, Richard Repasky, Joseph Rinkovsky, Steve Simms, Adam Sweeny, Peng Wang University Information Technology Services Indiana University

  2. Problem Description • Turn Windows desktop systems at IUB student labs into a scientific resource. • 2300 systems, 3 year replacement cycle • 1.5 Teraflops • Fast ethernet or better • Harvest idle cycles. SC'05, Seattle, WA

  3. Constraints • Systems dedicated to students using desktop office applications — not parallel scientific computing • Microsoft Windows environment • Daily software rebuild SC'05, Seattle, WA

  4. What could these systems be used for? • Many small computations and a few small messages • Master-worker • Parameter studies • Monte Carlo SC'05, Seattle, WA

  5. Assembling small ephemeral resources • Different parallel libraries have constraints of some form or the other • MPI not designed to handle ephemeral resources SC'05, Seattle, WA

  6. Solution • Simple Message Brokering Library (SMBL) • Limited replacement for MPI • Process and Port Manager (PPM) … Plus … • Condor NT • Job management • Web portal • Job submission SC'05, Seattle, WA

  7. The Big PictureWe’ll discuss each part in more detail next… The shaded box indicates components hosted on multiple desktop computers SC'05, Seattle, WA

  8. Portal • Creates and submits Condor files, handles data files • Apache based • PHP web interface • http://hydra.indiana.edu (IU users) • http://hydra.iu.teragrid.org (Teragrid users) SC'05, Seattle, WA

  9. Condor • Condor for Windows NT/2000/XP • “Vanilla universe” -- no support for check-pointing or parallelism • Provides: • Security • Match-making • Fair sharing • File transfer • Job submission, suspension, preemption, restart SC'05, Seattle, WA

  10. SMBL • In charge of message delivery for each parallel session • Client library implements selected MPI-like calls • Both server and client library based on TCP socket abstraction SC'05, Seattle, WA

  11. SMBL (Contd … ) Managing Temporary Workers • SMBL server maintains a dynamic pool of client process connections • Worker job manager hides details of ephemeral workers at the application level • Porting from MPI is fairly straight forward SC'05, Seattle, WA

  12. Process and Port Manager (PPM) • Assigns port/host to each parallel session • Starts the SMBL server and application processes on demand • Directs workers to their servers SC'05, Seattle, WA

  13. Once again … the big picture The shaded box indicates components hosted on multiple desktop computers SC'05, Seattle, WA

  14. System Layout • PPM, SMBL server and web portal running on Linux server -- Dual Intel Xeon 1.7 GHz, 2 GB memory and GigE inter-connect • STC Windows worker machines -- Combination of different OS (Windows 2000/XP) and network inter-connect speeds (GigE/100 Mbps/10 Mbps) SC'05, Seattle, WA

  15. Applications • FastDNAml-p • Parallel application, master-worker model, small granularity of work • Provides generic interface for parallel communication library (MPI, PVM, SMBL) • Reliability built in: Foreman process copes with delayed or lost workers • Blast • Meme SC'05, Seattle, WA

  16. Portal SC'05, Seattle, WA

  17. Applications – FastDNAml SC'05, Seattle, WA

  18. FastDNAml-p Performance SC'05, Seattle, WA

  19. Other Applications – Parallel MEME SC'05, Seattle, WA

  20. Other Applications – BLAST SC'05, Seattle, WA

  21. Utilization of Idle Cycles Red: total ownerBlue: total idleGreen: total Condor SC'05, Seattle, WA

  22. Recent Development • Hydra cluster Teragrid’ized! (Oct 2005) • Allow TG users to use resource • Virtual Host based solution – two different URLs for IU and Teragrid users • Teragrid users authenticate against different Kerberos server (PSC) • Still to-do • Usage accounting SC'05, Seattle, WA

  23. Work in Progress/Future Direction • Once again … Teragrid’ization of Hydra cluster • Usage Accounting – Report usage byTeragrid users • New Portal – JSR 168 compliant, certificate based authentication capability • Range of applications – Virtual machines, so forth SC'05, Seattle, WA

  24. Summary • Large parallel computing facility created at very low cost • SMBL parallel message passing library that can deal with ephemeral resources • PPM port broker that can handle multiple parallel sessions • SMBL (Open Source) Home – http://smbl.sourceforge.net SC'05, Seattle, WA

  25. Links and References • Hydra Portal • http://hydra.indiana.edu (IU users) • http://hydra.iu.teragrid.org (Teragrid users) • SMBL home page – http://smbl.sourceforge.net • Condor home page -- http://www.cs.wisc.edu/condor/ • IU Teragrid home page – http://iu.teragrid.org • Parallel FastDNAml – http://www.indiana.edu/~rac/hpc/fastDNAml • Blast -- http://www.ncbi.nlm.nih.gov/BLAST • Meme -- http://meme.sdsc.edu/meme/intro.html SC'05, Seattle, WA

More Related