DOCSLIB.ORG

NEC SX-Aurora TSUBASA Code Porting Workshop

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
NEC SX-Aurora TSUBASA Code Porting Workshop 2018/11/16 Agenda 10:00 – 10:30 SX Aurora Tsubasa : technology overview 10:30 – 11:30 Migration to SX-Aurora Tsubasa : compilers, CAU Kiel libraries, … NEC SX Aurora TSUBASA 11:30 – 12:00 RZ Kiel : overview Lunch break migration workshop 13:00 – 17:00 Hands-on session: porting, run-time, performance Dr. Jens-Olaf Beismann Senior Benchmarking Analyst NEC Deutschland GmbH SX Aurora TSUBASA Technology overview ° Dedicated vector processor ° High memory bandwidth ° Commodity processors ° De facto standard x86/Linux environment 4 © NEC Deutschland GmbH 2018 1 2018/11/16 Brand-new Vector Supercomputer Strategy Linux open environment TSUBASA : meaning “ wing ” in Japanese Linux asset High performance user 1.22TB/s / processor, 150GB/s / core Linux OS Vector Environment Engine Fortran/C/C++ programing, OpenMP Library Automatic vectorization/parallelization Tool x86 VE high performance High sustained performance on peripherals Application on x86/Linux environment x86/Linux 5 © NEC Deutschland GmbH 2018 6 © NEC Deutschland GmbH 2018 Architecture Inherited and Changed Aurora Architecture x86 node + Vector Engine (VE) VE capability is provided on x86/Linux environment Previous SX SX-Aurora TSUBASA VE OS Aurora Architecture Super-UX Application LINUX Application x86 server processor processor Supercomputer VE OS Linux core core OS SPU Mem. x86 SPU Mem. VPU VPU x86 node Rack Mount Servers Vector Engine storage storage VH VE SX-Aurora TSUBASA Vector Host Vector Engine Desktop Tower 7 © NEC Deutschland GmbH 2018 8 © NEC Deutschland GmbH 2018 2 2018/11/16 GPGPU and VE Processor GPGPU Architecture Aurora Architecture 2.45TF (@1.6GHZ) VE1.0 Spec. 307GFcore core core core AP Function cores/CPU 8 OS CUDA OS AP core ~307GF(DP) core core core core M M M M e e e e performance ~614GF(SP) m m m m o x86 GPGPU o o x86 VE o r r r r CPU ~2.45TF(DP) 0.4TB/s y PCIe y y PCIe y performance ~4.91TF(SP) 3TB/s exec exec cache Data Transmission Start Processing 16MB shared capacity Software controllable cache Result Transmission 16MB : OS I/O,etc memory : Function 1.22TB/s bandwidth memory exit exit End Processing 24, 48GB capacity 1.22TB/s Frequent PCIe transmission Whole AP is executed on VE PCIe bottleneck Avoiding PCIe bottleneck disadvantage Small memory Advantage Larger memory Programming difficulty Standard language HBM2 memory x 6 9 © NEC Deutschland GmbH 2018 10 © NEC Deutschland GmbH 2018 Product Core Architecture processor Card Single core VFMA0 VFMA0 VFMA0VFMA1 VFMA0VFMA1 VFMA0VFMA1 VFMA0VFMA1VFMA2 VFMA0VFMA1VFMA2 VFMA0VFMA1VFMA2 VFMA0VFMA1VFMA2ALU0 VFMA0VFMA1VFMA2ALU0 VFMA0VFMA1VFMA2ALU0 VFMA0VFMA1VFMA2ALU0ALU1 VFMA0VFMA1VFMA2ALU0ALU1 VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV Developed by NEC VFMA0VFMA1VFMA2ALU0ALU1DIV ■ VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV World’s highest memory bandwidth VFMA0VFMA1VFMA2ALU0ALU1DIV ■ VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA0VFMA1VFMA2ALU0ALU1DIV VFMA1VFMA2ALU0ALU1DIV VFMA1VFMA2ALU0ALU1DIV VFMA2ALU0ALU1DIV VFMA2ALU0ALU1DIV Peak Performance : Products of SX-Aurora TSUBASA VFMA2ALU0ALU1DIV ALU0ALU1DIV ALU0ALU1DIV 268.8GF = ALU0ALU1DIV ALU1DIV 32Flops/cycle x ALU1DIV 1.22TB/s / processor 400GB/s / core ALU1DIV DIV 2(FMA) x 3 x DIV (Ave. 150GB/s / core) 1.4GHz 1VE 2VE 4VE 8VE SPU CAU Kiel : 17.2 TF A100 Tower A300 Server A500 DLC Supercomputer Scalar Processing Unit 11 © NEC Deutschland GmbH 2018 12 © NEC Deutschland GmbH 2018 3 2018/11/16 Characteristics Fundamental Benchmarks x STREAM: VE is the highest sustained memory bandwidth / node HPL: VE provides competitive FLOPS capability Position Memory bandwidth / processor STREAM / node HPL / node Vector GPGPU Engine high spec. HPL/node STREAM/node ® specification Xeon standard standard special Xeon ® GPGPU Vector VE provides the highest memory VE provides same range HPL language Engine bandwidth sustained performance as SKL/KNL 13 © NEC Deutschland GmbH 2018 14 © NEC Deutschland GmbH 2018 Performance/Price HPCG High Price Competitiveness VE provides high HPCG performance per node and price - The highest STREAM sustained performance / price HPL and STREAM are bookends of benchmark, and HPCG stands - Competitive HPL sustained performance / price between them Performance HPCG / node HPCG / price STREAM / price HPL / price Characteristics HPL/price Aurora SKL STREAM/price Performanceratio Performanceratio Performanceratio VE provides the highest memory VE provides same range HPL 3x 3x Memory bandwidth Performance bandwidth/price sustained performance/price bound bound compared to Intel products 15 © NEC Deutschland GmbH 2018 16 © NEC Deutschland GmbH 2018 4 2018/11/16 Usability Programing Environment Vector Cross Compiler automatic vectorization automatic parallelization Fortran: F2003, F2008(partially) C: C11 C++: C++14 $ vi sample.c SX Aurora TSUBASA $ ncc sample.c OpenMP: OpenMP4.5 MPI: MPI3.1 User environment Execution Environment VH VE $ a.out execution 18 © NEC Deutschland GmbH 2018 Compilers Programming Environment Cross compilers : NEC supports the latest language standards along with GNU nfort compatibility ncc nc++ ▌C/C++ ISO/IEC 9899:2011 (aka C11) ISO/IEC 14882:2014 (aka C++14) Tools : ▌Fortran nld, nar, nranlib, … ISO/IEC 1539-1:2004 (aka Fortran 2003) ISO/IEC 1539-1:2010 (aka Fortran 2008) ▌OpenMP MPI wrappers : Version 4.5 mpinfort ▌Libraries mpincc libc mpinc++ MPI Version 3.1 (fully tuned for Aurora architecture) Numeric libraries (BLAS, FFT, Lapack, etc.) ▌Tools GNU Profiler (gprof) GNU Debugger (gdb), Eclipse Parallel Tools Platform (PTP) FtraceViewer / PROGINF 19 © NEC Deutschland GmbH 2018 20 © NEC Deutschland GmbH 2018 5 2018/11/16 Options Options -Caopt -O4 Compiler diagnostics / listings -Chopt -O3 -fdiag-vector=0|1|2 # more or less detailed -Cvopt -O2 vectorization diagnostics -Cvsafe -O1 -fdiag-parallel=0|1|2 -Cnoopt -O0 -fdiag-inline=0|1|2 -Omove -fmove-loop-invariants-unsafe -report-all # get both diagnostics and formatted listing in .L file -Onomovediv -fmove-loop-invariants -Onomove -fno-move-loop-invariants Default type size -fdefault-integer=4|8 -Popenmp -fopenmp -fdefault-real=4|8 -fdefault-double=8|16 -pi,auto -finline-functions # no cross-file inlining Cache usage … -mretain-[all|list-vector|none] 21 © NEC Deutschland GmbH 2018 22 © NEC Deutschland GmbH 2018 Directives Libraries !CDIR … !NEC$ … ▌NEC Library provides wide variety of functions NEC library is fully tuned for Aurora architecture nodep ivdep NEC Lib MKL BLAS P P LAPACK P P expand= n unroll( n) ScaLAPACK P P move move_unsafe FFT P P nomovediv move Random number generators P P nomove nomove Direct sparse solvers P P outerunroll=n outerloop_unroll(n) Iterative sparse solvers P P Functions for Statistics P P unroll= n unroll( n) Spline functions P P … Special functions P Directive conversion tool nfdirconv ! Approximation and Interpolation P Numerical Differentials/Integrals P Roots of Equations P Time series analysis P Sorting and ranking P 23 © NEC Deutschland GmbH 2018 24 © NEC Deutschland GmbH 2018 6 2018/11/16 UNIX system function interface Endianness SX-Aurora TSUBASA is little-endian ! (Former SXs were big- To use extensions like GETARG, FLUSH, ABORT , … subroutines, endian) compile with -use F90_UNIX[,F90_UNIX_ENV,…] export VE_FORT_UFMTENDIAN=10,11 (ALL) sets the unit number of an unformatted file to be treated as a file See Fortran Users’ Guide 8.2 for details in big-endian format. When the value of this variable is ALL , then all unit numbers are applied. Two or more unit numbers can be specified by comma delimitation. GNU Fortran extension : convert specifier open(10,file=‘test.dat’, form=‘unformatted’, & convert=‘big_endian’) Non-standard Fortran, but supported by nfort 25 © NEC Deutschland GmbH 2018 26 © NEC Deutschland GmbH 2018 Correctness Debugger Run-time errors…? Process Sets variables Functions Compile with -traceback export VE_TRACEBACK=FULL|ALL reduce optimization -fcheck=bounds (all) Stack/heap initialization –minit-stack=zero|nan export VE_INIT_HEAP=ZERO|NAN -mno-vector-fma Standard output export VE_FPE_ENABLE=(DIV,FOF,FUF,INV,INE) Source code Stack trace Standard error output (debugger) Eclipse parallel tools platform (PTP) VE plugin provides GUI debugging environment 27 © NEC Deutschland GmbH 2018 28 © NEC Deutschland GmbH 2018 7 2018/11/16 PROGINF performance information PROGINF performance information ******** Program Information ******** Real Time (sec) : 8783.021690 User Time (sec) : 8753.527852 Vector Time (sec) : 4959.702777 Inst. Count : 8018493848355 Compile with “-proginf” CompileV. Inst. with Count “-proginf” : 1081598389267 V. Element Count : 221178430822266 V. Load Element Count : 51426036073697 export VE_PROGINF=YES/DETAIL exportFLOP Count VE_PROGINF=YES/DETAIL : 140842692526140 MOPS : 29663.826745 MOPS (Real) : 29444.837925 MFLOPS : 16155.280253 MFLOPS (Real) : 16036.016282 A. V. Length : 204.492197 V. Op. Ratio (%) : 97.317633 L1 Cache Miss (sec) : 801.540473 CPU Port Conf. (sec) : 2.435367 V. Arith. Exec. (sec) : 2355.046188 V. Load Exec. (sec) : 2346.286974 VLD LLC Hit Element Ratio (%) : 79.566662 Power Throttling (sec) : 0.000000 Thermal Throttling (sec) : 0.000000 Memory Size Used (MB) : 10956.000000 Start Time (date) : Tue Nov 6 13:05:18 2018 CET End Time (date) : Tue Nov 6 15:31:41 2018
Load more

Recommended publications
  • User's Manual
    Management Number:OUCMC-super-技術-007-06 National University Corporation Osaka University Cybermedia Center User's manual NEC First Government & Public Solutions Division Summary 1. System Overview ................................................................................................. 1 1.1. Overall System View ....................................................................................... 1 1.2. Thress types of Computiong Environments ........................................................ 2 1.2.1. General-purpose CPU environment .............................................................. 2 1.2.2. Vector computing environment ................................................................... 3 1.2.3. GPGPU computing environment .................................................................. 5 1.3. Three types of Storage Areas ........................................................................... 6 1.3.1. Features.................................................................................................. 6 1.3.2. Various Data Access Methods ..................................................................... 6 1.4. Three types of Front-end nodes ....................................................................... 7 1.4.1. Features.................................................................................................. 7 1.4.2. HPC Front-end ......................................................................................... 7 1.4.1. HPDA Front-end ......................................................................................
    [Show full text]
  • DMI-HIRLAM on the NEC SX-6
    DMI-HIRLAM on the NEC SX-6 Maryanne Kmit Meteorological Research Division Danish Meteorological Institute Lyngbyvej 100 DK-2100 Copenhagen Ø Denmark 11th Workshop on the Use of High Performance Computing in Meteorology 25-29 October 2004 Outline • Danish Meteorological Institute (DMI) • Applications run on NEC SX-6 cluster • The NEC SX-6 cluster and access to it • DMI-HIRLAM - geographic areas, versions, and improvements • Strategy for utilization and operation of the system DMI - the Danish Meteorological Institute DMI’s mission: • Making observations • Communicating them to the general public • Developing scientific meteorology DMI’s responsibilities: • Serving the meteorological needs of the kingdom of Denmark • Denmark, the Faroes and Greenland, including territorial waters and airspace • Predicting and monitoring weather, climate and environmental conditions, on land and at sea Applications running on the NEC SX-6 cluster Operational usage: • Long DMI-HIRLAM forecasts 4 times a day • Wave model forecasts for the North Atlantic, the Danish waters, and for the Mediterranean Sea 4 times a day • Trajectory particle model and ozone forecasts for air quality Research usage: • Global climate simulations • Regional climate simulations • Research and development of operational and climate codes Cluster interconnect GE−int Completely closed Connection to GE−ext Switch internal network institute network Switch GE GE nec1 nec2 nec3 nec4 nec5 nec6 nec7 nec8 GE GE neci1 neci2 FC 4*1Gbit/s FC links per node azusa1 asama1 FC McData FC 4*1Gbit/s FC links per azusa fiber channel switch 8*1Gbit/s FC links per asama azusa2 asama2 FC 2*1Gbit/s FC links per lun Disk#0 Disk#1 Disk#2 Disk#3 Cluster specifications • NEC SX-6 (nec[12345678]) : 64M8 (8 vector nodes with 8 CPU each) – Desc.
    [Show full text]
  • Hardware Technology of the Earth Simulator 1
    Special Issue on High Performance Computing 27 Architecture and Hardware for HPC 1 Hardware Technology of the Earth Simulator 1 By Jun INASAKA,* Rikikazu IKEDA,* Kazuhiko UMEZAWA,* 5 Ko YOSHIKAWA,* Shitaka YAMADA† and Shigemune KITAWAKI‡ 5 1-1 This paper describes the hardware technologies of the supercomputer system “The Earth Simula- 1-2 ABSTRACT tor,” which has the highest performance in the world and was developed by ESRDC (the Earth 1-3 & 2-1 Simulator Research and Development Center)/NEC. The Earth Simulator has adopted NEC’s leading edge 2-2 10 technologies such as most advanced device technology and process technology to develop a high-speed and high-10 2-3 & 3-1 integrated LSI resulting in a one-chip vector processor. By combining this LSI technology with various advanced hardware technologies including high-density packaging, high-efficiency cooling technology against high heat dissipation and high-density cabling technology for the internal node shared memory system, ESRDC/ NEC has been successful in implementing the supercomputer system with its Linpack benchmark performance 15 of 35.86TFLOPS, which is the world’s highest performance (http://www.top500.org/ : the 20th TOP500 list of the15 world’s fastest supercomputers). KEYWORDS The Earth Simulator, Supercomputer, CMOS, LSI, Memory, Packaging, Build-up Printed Wiring Board (PWB), Connector, Cooling, Cable, Power supply 20 20 1. INTRODUCTION (Main Memory Unit) package are all interconnected with the fine coaxial cables to minimize the distances The Earth Simulator has adopted NEC’s most ad- between them and maximize the system packaging vanced CMOS technologies to integrate vector and density corresponding to the high-performance sys- 25 25 parallel processing functions for realizing a super- tem.
    [Show full text]
  • Shared-Memory Vector Systems Compared
    Shared-Memory Vector Systems Compared Robert Bell, CSIRO and Guy Robinson, Arctic Region Supercomputing Center ABSTRACT: The NEC SX-5 and the Cray SV1 are the only shared-memory vector computers currently being marketed. This compares with at least five models a few years ago (J90, T90, SX-4, Fujitsu and Hitachi), with IBM, Digital, Convex, CDC and others having fallen by the wayside in the early 1990s. In this presentation, some comparisons will be made between the architecture of the survivors, and some performance comparisons will be given on benchmark and applications codes, and in areas not usually presented in comparisons, e.g. file systems, network performance, gzip speeds, compilation speeds, scalability and tools and libraries. KEYWORDS: SX-5, SV1, shared-memory, vector systems averaged 95% on the larger node, and 92% on the smaller 1. Introduction node. HPCCC The SXes are supported by data storage systems – The Bureau of Meteorology and CSIRO in Australia SAM-FS for the Bureau, and DMF on a Cray J90se for established the High Performance Computing and CSIRO. Communications Centre (HPCCC) in 1997, to provide ARSC larger computational facilities than either party could The mission of the Arctic Region Supercomputing acquire separately. The main initial system was an NEC Centre is to support high performance computational SX-4, which has now been replaced by two NEC SX-5s. research in science and engineering with an emphasis on The current system is a dual-node SX-5/24M with 224 high latitudes and the Arctic. ARSC provides high Gbyte of memory, and this will become an SX-5/32M performance computational, visualisation and data storage with 224 Gbyte in July 2001.
    [Show full text]
  • Recent Supercomputing Development in Japan
    Supercomputing in Japan Yoshio Oyanagi Dean, Faculty of Information Science Kogakuin University 2006/4/24 1 Generations • Primordial Ages (1970’s) – Cray-1, 75APU, IAP • 1st Generation (1H of 1980’s) – Cyber205, XMP, S810, VP200, SX-2 • 2nd Generation (2H of 1980’s) – YMP, ETA-10, S820, VP2600, SX-3, nCUBE, CM-1 • 3rd Generation (1H of 1990’s) – C90, T3D, Cray-3, S3800, VPP500, SX-4, SP-1/2, CM-5, KSR2 （HPC ventures went out） • 4th Generation (2H of 1990’s) – T90, T3E, SV1, SP-3, Starfire, VPP300/700/5000, SX-5, SR2201/8000, ASCI(Red, Blue) • 5th Generation (1H of 2000’s) – ASCI，TeraGrid，BlueGene/L，X1, Origin,Power4/5, ES, SX- 6/7/8, PP HPC2500, SR11000, …. 2006/4/24 2 Primordial Ages (1970’s) 1974 DAP, BSP and HEP started 1975 ILLIAC IV becomes operational 1976 Cray-1 delivered to LANL 80MHz, 160MF 1976 FPS AP-120B delivered 1977 FACOM230-75 APU 22MF 1978 HITAC M-180 IAP 1978 PAX project started (Hoshino and Kawai) 1979 HEP operational as a single processor 1979 HITAC M-200H IAP 48MF 1982 NEC ACOS-1000 IAP 28MF 1982 HITAC M280H IAP 67MF 2006/4/24 3 Characteristics of Japanese SC’s 1. Manufactured by main-frame vendors with semiconductor facilities (not ventures) 2. Vector processors are attached to mainframes 3. HITAC IAP a) memory-to-memory b) summation, inner product and 1st order recurrence can be vectorized c) vectorization of loops with IF’s (M280) 4. No high performance parallel machines 2006/4/24 4 1st Generation (1H of 1980’s) 1981 FPS-164 (64 bits) 1981 CDC Cyber 205 400MF 1982 Cray XMP-2 Steve Chen 630MF 1982 Cosmic Cube in Caltech, Alliant FX/8 delivered, HEP installed 1983 HITAC S-810/20 630MF 1983 FACOM VP-200 570MF 1983 Encore, Sequent and TMC founded, ETA span off from CDC 2006/4/24 5 1st Generation (1H of 1980’s) (continued) 1984 Multiflow founded 1984 Cray XMP-4 1260MF 1984 PAX-64J completed (Tsukuba) 1985 NEC SX-2 1300MF 1985 FPS-264 1985 Convex C1 1985 Cray-2 1952MF 1985 Intel iPSC/1, T414, NCUBE/1, Stellar, Ardent… 1985 FACOM VP-400 1140MF 1986 CM-1 shipped, FPS T-series (max 1TF!!) 2006/4/24 6 Characteristics of Japanese SC in the 1st G.
    [Show full text]
  • Hardware-Oblivious SIMD Parallelism for In-Memory Column-Stores
    Hardware-Oblivious SIMD Parallelism for In-Memory Column-Stores Template Vector Library — General Approach and Opportunities Annett Ungethüm, Johannes Pietrzyk, Erich Focht Patrick Damme, Alexander Krause, High Performance Computing Europe Dirk Habich, Wolfgang Lehner NEC Deutschland GmbH Database Systems Group Stuttgart, Germany Technische Universität Dresden [email protected] Dresden, Germany fi[email protected] ABSTRACT be mapped to a variety of parallel processing architectures Vectorization based on the Single Instruction Multiple Data like many-core CPUs or GPUs. Another recent hardware- (SIMD) parallel paradigm is a core technique to improve oblivious approach is the data processing interface DPI for query processing performance especially in state-of-the-art modern networks [2]. in-memory column-stores. In mainstream CPUs, vectoriza- In addition to parallel processing over multiple cores, tion is offered by a large number of powerful SIMD exten- vector processing according to the Single Instruction sions growing not only in vector size but also in terms of Multiple Data (SIMD) parallel paradigm is also a heavily complexity of the provided instruction sets. However, pro- used hardware-driven technique to improve the query performance in particular for in-memory column-store gramming with vector extensions is a non-trivial task and 1 currently accomplished in a hardware-conscious way. This database systems [10, 14, 21, 26, 27]. On mainstream implementation process is not only error-prone but also con- CPUs, this vectorization is done using SIMD extensions nected with quite some effort for embracing new vector ex- such as Intel's SSE (Streaming SIMD extensions) or AVX tensions or porting to other vector extensions.
    [Show full text]
  • Performance Evaluation of Supercomputers Using HPCC and IMB Benchmarks
    Performance Evaluation of Supercomputers using HPCC and IMB Benchmarks Subhash Saini1, Robert Ciotti1,Brian T. N. Gunney2, Thomas E. Spelce2, Alice Koniges2, Don Dossa2, Panagiotis Adamidis3, Rolf Rabenseifner3, Sunil R. Tiyyagura3, Matthias Mueller4, and Rod Fatoohi5 1Advanced Supercomputing Division NASA Ames Research Center Moffett Field, California 94035, USA {ssaini, ciotti}@nas.nasa.gov 4ZIH, TU Dresden. Zellescher Weg 12, D-01069 Dresden, Germany 2Lawrence Livermore National Laboratory [email protected] Livermore, California 94550, USA {gunney, koniges, dossa1}@llnl.gov 5San Jose State University 3 One Washington Square High-Performance Computing-Center (HLRS) San Jose, California 95192 Allmandring 30, D-70550 Stuttgart, Germany [email protected] University of Stuttgart {adamidis, rabenseifner, sunil}@hlrs.de Abstract paradigm has become the de facto standard in programming high-end parallel computers. As a result, the performance of a majority of applications depends on the The HPC Challenge (HPCC) benchmark suite and the performance of the MPI functions as implemented on Intel MPI Benchmark (IMB) are used to compare and these systems. Simple bandwidth and latency tests are two evaluate the combined performance of processor, memory traditional metrics for assessing the performance of the subsystem and interconnect fabric of five leading interconnect fabric of the system. However, simple supercomputers - SGI Altix BX2, Cray X1, Cray Opteron measures of these two are not adequate to predict the Cluster, Dell Xeon cluster, and NEC SX-8. These five performance for real world applications. For instance, systems use five different networks (SGI NUMALINK4, traditional methods highlight the performance of network Cray network, Myrinet, InfiniBand, and NEC IXS).
    [Show full text]
  • Optimizing Sparse Matrix-Vector Multiplication in NEC SX-Aurora Vector Engine
    Optimizing Sparse Matrix-Vector Multiplication in NEC SX-Aurora Vector Engine Constantino Gómez1, Marc Casas1, Filippo Mantovani1, and Erich Focht2 1Barcelona Supercomputing Center, {first.last}@bsc.es 2NEC HPC Europe (Germany), {first.last}@EMEA.NEC.COM August 14, 2020 Abstract Sparse Matrix-Vector multiplication (SpMV) is an essential piece of code used in many High Performance Computing (HPC) applications. As previous literature shows, achieving ecient vectorization and performance in modern multi-core systems is nothing straightforward. It is important then to revisit the current state- of-the-art matrix formats and optimizations to be able to deliver high performance in long vector architectures. In this tech-report, we describe how to develop an ef- ficient implementation that achieves high throughput in the NEC Vector Engine: a 256 element-long vector architecture. Combining several pre-processing and ker- nel optimizations we obtain an average 12% improvement over a base SELL-C-σ implementation on a heterogeneous set of 24 matrices. 1 Introduction The Sparse Matrix-Vector (SpMV) product is a ubiquitous kernel in the context of High- Performance Computing (HPC). For example, discretization schemes like the finite dif- ferences or finite element methods to solve Partial Dierential Equations (PDE) pro- duce linear systems with a highly sparse matrix. Such linear systems are typically solved via iterative methods, which require an extensive use of SpMV across the whole execution. In addition, emerging workloads from the data-analytics area also require the manipulation of highly irregular and sparse matrices via SpMV. Therefore, the e- cient execution of this fundamental linear algebra kernel is of paramount importance.
    [Show full text]
  • SX-Aurora TSUBASA Program Execution Quick Guide
    SX-Aurora TSUBASA Program Execution Quick Guide Proprietary Notice The information disclosed in this document is the property of NEC Corporation (NEC) and/or its licensors. NEC and/or its licensors, as appropriate, reserve all patent, copyright, and other proprietary rights to this document, including all design, manufacturing, reproduction, use and sales rights thereto, except to the extent said rights are expressly granted to others. The information in this document is subject to change at any time, without notice. Linux is the registered trademark of Linus Torvalds in the United States and other countries. InfiniBand is a trademark of InfiniBand Trade Association. In addition, mentioned company name and product name are a registered trademark or a trademark of each company. Copyright 2018, 2021 NEC Corporation - i - Preface The SX-Aurora TSUBASA Program Execution Quick Guide is the document for those using SX-Aurora TSUBASA for the first time. It explains the basic usage of the SX- Aurora TSUBASA software products; the compilers, MPI, NQSV, PROGINF, and FTRACE. This guide assumes the following installation, setup, and knowledge. VEOS and the necessary software have been installed and set up. Users are able to log in to the system or use the job scheduler NQSV (NEC Network Queuing System V) or PBS. Users have knowledge of Fortran compiler (nfort), C compiler (ncc), C++ compiler (nc++), and NEC MPI. This guide assumes the version of VEOS is 2.3.0 or later. The version of VEOS can be confirmed by the following way. $ rpm -q veos veos-2.3.0-1.el7.x86_64 VH/VE hybrid MPI execution is available in NEC MPI version 2.3.0 and later.
    [Show full text]
  • NEC SX-Aurora Tsubasa System at ICM UW User Guide
    NEC SX-Aurora Tsubasa system at ICM UW User Guide NEC SX-Aurora Tsubasa: User Guide Last revision: 2020-04-09 by M. Hermanowicz <[email protected]> This document aims to provide basic information on how to use the NEC SX-Aurora Tsubasa system available at ICM UW computational facility. The contents herein are based on a number of documents, as referenced in the text, to provide a concise quick start guide and suggest further reading material for the ICM users. Contents 1 Introduction 1 2 Basic usage 1 3 SOL: Transparent Neural Network Acceleration 3 1 Introduction NEC SX-Aurora Tsubasa, announced in 2017, is a vector processor (vector engine, VE) belonging to the SX architecture line which has been developed by NEC Corporation since mid-1980s [1]. Unlike its stand-alone predecessors, Tsubasa has been designed as a PCIe card working within and being operated by an x86 64 host server (vector host, VH) running a distribution of the GNU/Linux operating system. The latter provides a complete software development environment for the connected VEs and runs Vec- tor Engine Operating System (VEOS) which, in turn, serves as operating system to the VE programs. [2]. ICM UW provides its users with a NEC SX-Aurora Tsubasa installation as part of the Rysy cluster { see Table 1 { within the ve partition. Vector Host (VH) Vector Engine (VE) CPU Model Intel Xeon Gold 6126 NEC SX-Aurora Tsubasa A300-8 CPU Cores 2 × 12 8 × 8 RAM [GB] 192 8 × 48 Table 1: NEC SX-Aurora Tsubasa installation at ICM UW: the ve partition of the Rysy cluster 2 Basic usage To use the Tsubasa installation users must access the login node first at hpc.icm.edu.pl through SSH [3] and then establish a further connection to the Rysy cluster as in Listing 1.
    [Show full text]
  • Vampirtrace 5.14.4 User Manual
    VampirTrace 5.14.4 with extended accelerator support User Manual TU Dresden Center for Information Services and High Performance Computing (ZIH) 01062 Dresden Germany http://www.tu-dresden.de/zih http://www.tu-dresden.de/zih/vampirtrace Contact: [email protected] ii Contents Contents 1. Introduction1 2. Instrumentation5 2.1. Compiler Wrappers...........................5 2.2. Instrumentation Types.........................7 2.3. Automatic Instrumentation.......................7 2.3.1. Supported Compilers.....................8 2.3.2. Notes for Using the GNU, Intel, PathScale, or Open64 Com- piler...............................8 2.3.3. Notes on Instrumentation of Inline Functions........9 2.3.4. Instrumentation of Loops with OpenUH Compiler......9 2.4. Manual Instrumentation........................9 2.4.1. Using the VampirTrace API..................9 2.4.2. Measurement Controls..................... 10 2.5. Source Instrumentation Using PDT/TAU............... 12 2.6. Binary Instrumentation Using Dyninst................ 13 2.6.1. Static Binary Instrumentation................. 13 2.7. Runtime Instrumentation Using VTRun................ 14 2.8. Tracing Java Applications Using JVMTI................ 14 2.9. Tracing Calls to 3rd-Party Libraries.................. 15 3. Runtime Measurement 17 3.1. Trace File Name and Location..................... 17 3.2. Environment Variables......................... 17 3.3. Influencing Trace Buffer Size..................... 21 3.4. Profiling an Application......................... 22 3.5. Unification of Local Traces....................... 22 3.6. Synchronized Buffer Flush....................... 23 3.7. Enhanced Timer Synchronization................... 23 3.8. Environment Configuration Using VTSetup............. 24 4. Recording Additional Events and Counters 27 4.1. Hardware Performance Counters................... 27 4.2. Resource Usage Counters...................... 28 4.3. Memory Allocation Counter...................... 28 4.4. CPU ID Counter............................ 29 iii Contents 4.5.
    [Show full text]
  • The Nec Sx-6 Asia Nec Hpc Marketing Supercomputer with Single-Chip Vector Processor Promotion Division
    SX-6 Datenblatt Single Node 28.09.2001 9:37 Uhr Seite 1 Courtesy of HLRS, Stuttgart/Germany, Cave Simulation Courtesy of ESI Group For Information Contact: THE NEC SX-6 ̈ ASIA NEC HPC MARKETING SUPERCOMPUTER WITH SINGLE-CHIP VECTOR PROCESSOR PROMOTION DIVISION 7-1 Shiba, 5-chome Minato-ku, Tokyo 108-8001 SOFTWARE Japan +81-3-3798-9131 phone +81-3-3798-9132 fax [email protected] Operating System and Applications ̈ EUROPE NEC EUROPEAN With traditional NEC reliabili- Applications development is SUPERCOMPUTER SYSTEMS ty and the SUPER-UX operating made easy through the simplicity system, now in its 12th year, SX-6 of shared memory programming Prinzenallee 11 is designed for production sites to within a node, and portability is D-40549 Düsseldorf Germany perform production computing. assured by industry-standard MPI +49-211-5369-0 phone All the functions other systems and OpenMP support. NEC’s +49-211-5369-199 fax promise, like checkpoint-restart PSUITE Integrated Development [email protected] or a robust batch environment, Environment provides all of the ̈ LATIN AMERICA are available today. tools and utilities necessary under NEC DO BRASIL S.A. SX-OFFICE All third party applications rel- a single package for project man- evant to parallel vector supercom- agement, editing, compiling, opti- Rua Arabé, 71 CEP 04042-070 V.Clementino puters are available and provide mizing, and test/debugging. The São Paulo SP industry-leading performance. cross development environment Brasil Turnaround time for solutions is PSUITE is available on all popular +55-11-5591-7147 phone minimized.
    [Show full text]