NAS Parallel Benchmarks

NAS Parallel Benchmarks
Original author(s) NASA Numerical Aerodynamic Simulation Program
Developer(s) NASA Advanced Supercomputing Division
Stable release
3.3.1
Development status Active
Platform Cross-platform
Website www.nas.nasa.gov/Software/NPB/

The NAS Parallel Benchmarks (NPB) are a set of benchmarks targeting performance evaluation of highly parallel supercomputers. They are developed and maintained by the NASA Advanced Supercomputing (NAS) Division (formerly the NASA Numerical Aerodynamic Simulation Program) based at the NASA Ames Research Center. NAS solicits performance results for NPB from all sources.[1]

History

Motivation

Traditional benchmarks that existed before NPB, such as the Livermore loops, the LINPACK Benchmark and the NAS Kernel Benchmark Program, were usually specialized for vector computers. They generally suffered from inadequacies including parallelism-impeding tuning restrictions and insufficient problem sizes, which rendered them inappropriate for highly parallel systems. Equally unsuitable were full-scale application benchmarks due to high porting cost and unavailability of automatic software parallelization tools.[2] As a result, NPB were developed in 1991[3] and released in 1992[4] to address the ensuing lack of benchmarks applicable to highly parallel machines.

NPB 1

The first specification of NPB recognized that the benchmarks should feature

In the light of these guidelines, it was deemed the only viable approach to use a collection of "paper-and-pencil" benchmarks that specified a set of problems only algorithmically and left most implementation details to the implementer's discretion under certain necessary limits.

NPB 1 defined eight benchmarks, each in two problem sizes dubbed Class A and Class B. Sample codes written in Fortran 77 were supplied. They used a small problem size Class S and were not intended for benchmarking purposes.[2]

NPB 2

Since its release, NPB 1 displayed two major weaknesses. Firstly, due to its "paper-and-pencil" specification, computer vendors usually highly tuned their implementations so that their performance became difficult for scientific programmers to attain. Secondly, many of these implementation were proprietary and not publicly available, effectively concealing their optimizing techniques. Secondly, problem sizes of NPB 1 lagged behind the development of supercomputers as the latter continued to evolve.[3]

NPB 2, released in 1996,[5][6] came with source code implementations for five out of eight benchmarks defined in NPB 1 to supplement but not replace NPB 1. It extended the benchmarks with an up-to-date problem size Class C. It also amended the rules for submitting benchmarking results. The new rules included explicit requests for output files as well as modified source files and build scripts to ensure public availability of the modifications and reproducibility of the results.[3]

NPB 2.2 contained implementations of two more benchmarks.[5] NPB 2.3 of 1997 was the first complete implementation in MPI.[4] It shipped with serial versions of the benchmarks consistent with the parallel versions and defined a problem size Class W for small-memory systems.[7] NPB 2.4 of 2002 offered a new MPI implementation and introduced another still larger problem size Class D.[6] It also augmented one benchmark with I/O-intensive subtypes.[4]

NPB 3

NPB 3 retained the MPI implementation from NPB 2 and came in more flavors, namely OpenMP,[8] Java[9] and High Performance Fortran.[10] These new parallel implementations were derived from the serial codes in NPB 2.3 with additional optimizations.[7] NPB 3.1 and NPB 3.2 added three more benchmarks,[11][12] which, however, were not available across all implementations; NPB 3.3 introduced a Class E problem size.[7] Based on the single-zone NPB 3, a set of multi-zone benchmarks taking advantage of the MPI/OpenMP hybrid programming model were released under the name NPB-Multi-Zone (NPB-MZ) for "testing the effectiveness of multi-level and hybrid parallelization paradigms and tools".[1][13]

The benchmarks

As of NPB 3.3, eleven benchmarks are defined as summarized in the following table.

Benchmark Name derived from[2] Available since Description[2] Remarks
MG MultiGrid NPB 1[2] Approximate the solution to a three-dimensional discrete Poisson equation using the V-cycle multigrid method
CG Conjugate Gradiant Estimate the smallest eigenvalue of a large sparse symmetric positive-definite matrix using the inverse iteration with the conjugate gradient method as a subroutine for solving systems of linear equations
FT Fast Fourier Transform Solve a three-dimensional partial differential equation (PDE) using the fast Fourier transform (FFT)
IS Integer Sort Sort small integers using the bucket sort[5]
EP Embarrassingly Parallel Generate independent Gaussian random variates using the Marsaglia polar method
BT Block Tridiagonal Solve a synthetic system of nonlinear PDEs using three different algorithms involving block tridiagonal, scalar pentadiagonal and symmetric successive over-relaxation (SSOR) solver kernels, respectively
  • The BT benchmark has I/O-intensive subtypes[4]
  • All three benchmarks have multi-zone versions[13]
SP Scalar Pentadiagonal[6]
LU Lower-Upper symmetric Gauss-Seidel[6]
UA Unstructured Adaptive[11] NPB 3.1[7] Solve Heat equation with convection and diffusion from moving ball. Mesh is adaptive and recomputed at every 5th step.
DC Data Cube operator[12]
DT Data Traffic[7] NPB 3.2[7]

References

  1. 1 2 "NAS Parallel Benchmarks Changes". NASA Advanced Supercomputing Division. Retrieved 2009-02-23.
  2. 1 2 3 4 5 Baily, D.; Barscz, E.; Barton, J.; Browning, D.; Carter, R.; Dagum, L.; Fatoohi, R.; Fineberg, S.; Frederickson, P.; Weeratunga, S. (March 1994), "The NAS Parallel Benchmarks" (PDF), NAS Technical Report RNR-94-007, NASA Ames Research Center, Moffett Field, CA
  3. 1 2 3 Bailey, D.; Harris, T.; Saphir, W.; van der Wijngaart, R.; Woo, A.; Yarrow, M. (December 1995), "The NAS Parallel Benchmarks 2.0" (PDF), NAS Technical Report NAS-95-020, NASA Ames Research Center, Moffett Field, CA
  4. 1 2 3 4 Wong, P.; van der Wijngaart, R. (January 2003), "NAS Parallel Benchmarks I/O Version 2.4" (PDF), NAS Technical Report NAS-03-002, NASA Ames Research Center, Moffett Field, CA
  5. 1 2 3 Saphir, W.; van der Wijngaart, R.; Woo, A.; Yarrow, M., New Implementations and Results for the NAS Parallel Benchmarks 2 (PDF), NASA Ames Research Center, Moffett Field, CA
  6. 1 2 3 4 van der Wijngaart, R. (October 2002), "NAS Parallel Benchmarks Version 2.4" (PDF), NAS Technical Report NAS-02-007, NASA Ames Research Center, Moffett Field, CA
  7. 1 2 3 4 5 6 "NAS Parallel Benchmarks Changes". NASA Advanced Supercomputing Division. Retrieved 2009-03-17.
  8. ↑ Jin, H.; Frumkin, M.; Yan, J. (October 1999), "The OpenMP Implementation of NAS Parallel Benchmarks and Its Performance" (PDF), NAS Technical Report NAS-99-011, NASA Ames Research Center, Moffett Field, CA
  9. ↑ Frumkin, M.; Schultz, M.; Jin, H.; Yan, J., "Implementation of the NAS Parallel Benchmarks in Java" (PDF), NAS Technical Report NAS-02-009, NASA Ames Research Center, Moffett Field, CA
  10. ↑ Frumkin, M.; Jin, H.; Yan, J. (September 1998), "Implementation of NAS Parallel Benchmarks in High Performance Fortran" (PDF), NAS Technical Report NAS-98-009, NASA Ames Research Center, Moffett Field, CA
  11. 1 2 Feng, H.; van der Wijngaart, F.; Biswas, R.; Mavriplis, C. (July 2004), "Unstructured Adaptive (UA) NAS Parallel Benchmark, Version 1.0" (PDF), NAS Technical Report NAS-04-006, NASA Ames Research Center, Moffett Field, CA
  12. 1 2 Frumkin, M.; Shabanov, L. (September 2004), "Benchmarking Memory Performance with the Data Cube Operator" (PDF), NAS Technical Report NAS-04-013, NASA Ames Research Center, Moffett Field, CA
  13. 1 2 van der Wijngaart, R.; Jin, H. (July 2003), "NAS Parallel Benchmarks, Multi-Zone Versions" (PDF), NAS Technical Report NAS-03-010, NASA Ames Research Center, Moffett Field, CA
This article is issued from Wikipedia - version of the 3/11/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.