170 likes | 179 Views
This article explores the use of grid computing for improving code speed, specifically in the context of the Cluster Finder use case in the study of galaxy clusters. It discusses the benefits, challenges, and opportunities for parallelization and distribution, as well as the desire for support in code portability.
E N D
The Grid from a User´s Perspective: The Cluster Finder Use Case Art Carlson AstroGrid-D, Heidelberg, 24 July 2006
The bottom line • The main thing I want the grid for is improving my top speed. • I know I have to parallelize my code myself, but I want some support doing it. • I don‘t want to have to port my code to more than one environment.
No shortage of data or questions • More sky: 140 sq-deg → 10,000 sq-deg • Deeper surveys: 2000 times more data • Parameter studies: e.g. Cluster model • More sophisticated analysis: e.g. More spectral/energy channels
Where does the Grid come in? • Speed – but sprinting, not marathon • Get it by • Parallelization • Distribution • Pleasant side effects • Collaboration • Logistics • Monitoring and restart
Distribution: file management • Read from data base or source file or cache • Written locally or remotely, in one file or several • In ASCII or binary or data base format • I don‘t care about any of that
Distribution: execution Many opportunities for trouble: • Architecture • Compiler • System routines • Libraries Less so with Java, more so with Fortran
Distribution: execution • Installation – the tried and true method, but too much work and a shame • Metadata – also a lot of work and not foolproof • Self-tests – recognizes trouble early and reliably, but doesn‘t solve the problems • Virtual environment???
The bottom line • The main thing I want the grid for is improving my top speed. • I know I have to parallelize my code myself, but I want some support doing it. • I don‘t want to have to port my code to more than one environment.