ME964 High Performance Computing for Engineering Applications

The Eclipse IDE Parallel Computing: why and why now?

February 2, 2012

Dan Negrut, 2012 ME964 UW-Madison

I have traveled the length and breadth of this country and talked with the best people, and I can assure you that data processing is a fad that won't last out the year. The editor in charge of business books for Prentice Hall, 1957.

Before We Get Started

Last time

Wrap up quick overview of C Programming Super quick intro to gdb (debugging tool under Linux) Learn how to login into Euler Quick intro on Mercurial for revision control for handling of your assignments

Today

Getting started with Eclipse, an integrated development environment (Andrew) Parallel computing: why and why now? (Dan)

First assignment sent out last week, available on the class website

HW 1 due tonight, at 11:59 PM Post related questions to the forum

2

Eclipse
~ An Integrated Development Environment ~

Eclipse on Euler

Eclipse 3.7 (Indigo)

Includes Parallel Tools Platform, Linux Tools, CMakeEditor Will be installed into your home directory

Had issues installing system-wide

Other versions available just ask Managed by Environment Modules

Enabling Eclipse

Open Terminal

Load the Eclipse module by typing

>> module load eclipse/3.7

The first time will take a while (its installing)

Tell modules to load Eclipse by default

>> module initadd eclipse/3.7

Start Eclipse

eclipse

Creating a Project

File > New > C (C++) Project

Select the Linux GCC toolchain

Preferably put the source code in your repo

Or copy it by hand later

Enable both Debug and Release configs

All this can be managed by CMake (later)

Build/Run/Debug

Build with the hammer

Problems will be displayed at the bottom, under Problems and Console

Run with the play button

Output is shown under Console

Debug with the bug

Switches to the Debug perspective Frontend to GDB

But not cuda-gdb (yet)

Stack trace

Variables in scope, breakpoints, etc.

Source code

Parallel Computing: Why? & Why Now?

10

The Long View

Sequential computing has been losing steam recently

The rest of the decade seems to belong to parallel computing

11

High Performance Computing (HPC): Why, and Why Now.

Objectives of this course segment:

Discuss some barriers facing the traditional sequential computation model Discuss some solutions suggested by recent trends in the hardware and software industries

Overview of hardware and software solutions in relation to parallel computing

12

Acknowledgements

Presentation on this topic includes material due to

Hennessy and Patterson (Computer Architecture, 4th edition) John Owens, UC-Davis Daro Surez, Universidad de Zaragoza John Cavazos, University of Delaware Others, as indicated on various slides I apologize if I included a slide and didnt give credit where was due

13

CPU Speed Evolution

[log scale]

Courtesy of Elsevier: from Computer Architecture, Hennessey and Patterson, fourth edition

14

we can expect very little improvement in serial performance of general purpose CPUs. So if we are to continue to enjoy improvements in software capability at the rate we have become accustomed to, we must use parallel computing. This will have a profound effect on commercial software development including the languages, compilers, operating systems, and software development tools, which will in turn have an equally profound effect on computer and computational scientists.
John L. Manferdelli, Microsoft Corporation Distinguished Engineer, leads the eXtreme Computing Group (XCG) System, Security and Quantum Computing Research Group

15

15

Three Walls to Serial Performance

Memory Wall
Source: The Many-Core Inflection Point for Mass Market Computer Systems, by John L. Manferdelli, Microsoft Corporation
http://www.ctwatch.org/quarterly/articles /2007/02/the-many-core-inflection-pointfor-mass-market-computer-systems/

Instruction Level Parallelism (ILP) Wall

Power Wall

16

Memory Wall

Memory Wall: What is it? The growing disparity of speed between CPU and memory outside the CPU chip.

Memory latency is a barrier to computer performance improvements

Current architectures have ever growing caches to improve the average memory reference time to fetch or write instructions or data

Memory Wall: due to latency and limited communication bandwidth beyond chip boundaries.

From 1986 to 2000, CPU speed improved at an annual rate of 55% while memory access speed only improved at 10%
17

Memory Bandwidths
[typical embedded, desktop and server computers]

Courtesy of Elsevier, Computer Architecture, Hennessey and Patterson, fourth edition

18

Memory Speed:
Widening of the Processor-DRAM Performance Gap

The processor: victim of its own success

So fast it left the memory behind The CPU-Memory duo cant move as fast as youd like (based on CPU top speeds) with a sluggish memory

Plot on next slide shows on a *log* scale the increasing gap between CPU and memory The memory baseline: 64 KB DRAM in 1980 Memory speed increasing at a rate of approx 1.07/year

However, processors improved

1.25/year (1980-1986) 1.52/year (1986-2004) 1.20/year (2004-2010)

19

Memory Speed:
Widening of the Processor-DRAM Performance Gap

Courtesy of Elsevier, Computer Architecture, Hennessey and Patterson, fourth edition

20

Memory Latency vs. Memory Bandwidth

Latency: the amount of time it takes for an operation to complete

Measured in seconds The utility ping in Linux measures the latency of a network For memory transactions: send 32 bits to destination and back, measure how much time it takes ! gives you latency

Bandwidth: how much data can be transferred per second

You can talk about bandwidth for memory but also for a network (Ethernet, Infiniband, modem, DSL, etc.)

Improving Latency and Bandwidth

The job of the colleagues in Electrical Engineering Once in a while, our friends in Materials Science deliver a breakthrough Promising technology: optic networks and layered memory on top of chip

21

Memory Latency vs. Memory Bandwidth

Memory Access Latency is significantly more challenging to improve as opposed to improving Memory Bandwidth Improving Bandwidth: add more pipes.

Requires more pins that come out of the chip for DRAM, for instance. Tricky

Improving Latency: not obvious what the solution is

Analogy:

If you carry commuters with a train, add more cars to a train to increase bandwidth Improving latency requires the construction of high speed trains

Very expensive Requires qualitatively new technology

22

Latency vs. Bandwidth Improvements Over the Last 25 years

Courtesy of Elsevier, Computer Architecture, Hennessey and Patterson, fourth edition

23

The 3D Memory Cube

[possible breakthrough?]

Micron's Hybrid Memory Cube (HMC) features a stack of individual chips connected by vertical pipelines or vias, shown in the pic. IBMs new 3-D manufacturing 32 nm technology, used to connect the 3D micro structure, will be the foundation for commercial production of the new memory cube HMC prototypes clock in with bandwidth of 128 gigabytes per second (GB/s).

By comparison, current devices deliver roughly 15 GB/s.

HMC also requires 70 percent less energy to transfer data HMC offers a small form factor just 10 percent of the footprint of conventional memory.

http://www-03.ibm.com/press/us/en/pressrelease/36125.wss

24

Memory Wall, Conclusions

[IMPORTANT ME964 SLIDE]

Memory trashing is what kills execution speed Many times you will see that when you run your application:

You are far away from reaching top speed of the chip AND You are at top speed for your memory

If this is the case, you are trashing the memory Means that basically you are doing one or both of the following

Move large amounts of data around Move data often

Memory Access Patterns Golden To/From Registers Superior To/From Cache Trouble To/From RAM Salary cut To/From Disk

25

[One Slide Detour]

Nomenclature

Computer architecture its three facets are as follows:

Instruction set architecture (ISA) the set of instructions that the processor can do

Examples: RISC, X86, ARM, etc. The job of the friends in the Computer Science department

Microarchitecture (organization) cache levels, amount of cache at each level, etc.

The detailed low level organization of the chip that ensures that the ISA is implemented and performs according to specifications Mostly CS but Electrical Engineering is relevant

System design how to connect things on a chip, buses, memory controllers, etc.

Mostly a job for our friends in the Electrical Engineering

26

Instruction Level Parallelism (ILP)

ILP: a relevant factor in reducing execution times after 1985

The basic idea:

Improve performance by overlapping execution of independent instructions

Two approaches to discovering ILP

Dynamic: relies on hardware to discover/exploit parallelism dynamically at run time

It is the dominant one in the market

Static: relies on compiler to identify parallelism in the code and leverage it (VLIW)

Examples where ILP expected to improve efficiency

for( int=0; i<1000; i++) x[i] = x[i] + y[i]; 1. e = a + b 2. f = c + d 3. g = e * f

27

ILP: Various Angles of Attack

Instruction pipelining: the execution of multiple instructions can be partially overlapped; where each instructions is divided into series of sub-steps (termed: micro-operations)

Superscalar execution: multiple execution units are used to execute multiple instructions in parallel

Out-of-order execution: instructions execute in any order but without violating data dependencies

Register renaming: a technique used to avoid unnecessary serialization of program instructions caused by the reuse of registers by those instructions, in order to enable out-of-order execution

Speculative execution: allows the execution of complete instructions or parts of instructions before being sure whether this execution is required

Branch prediction: used to avoid delays (termed: stalls). Used in combination with speculative execution.
28

The ILP Wall

For ILP to make a dent, you need large blocks of instructions that can be [attempted to be] run in parallel Duplicate hardware speculatively executes future instructions before the results of current instructions are known, while providing hardware safeguards to prevent the errors that might be caused by out of order execution

Branches must be guessed to decide what instructions to execute simultaneously If you guessed wrong, you throw away that part of the result
Data dependencies may prevent successive instructions from executing in parallel, even if there are no branches

29

The ILP Wall

ILP, the good:

Existing programs enjoy performance benefits without any modification Recompiling them is beneficial but entirely up to you as long as you stick with the same ISA (for instance, if you go from Pentium 2 to Pentium 4 you dont have to recompile your executable)

ILP, the bad:

Improvements are difficult to forecast since the speculation success is difficult to predict Moreover, ILP causes a super-linear increase in execution unit complexity (and associated power consumption) without linear speedup.

ILP, the ugly: serial performance acceleration using ILP has stalled because of these effects
30

The Power Wall

Power, and not manufacturing, limits traditional general purpose microarchitecture improvements (F. Pollack, Intel Fellow) Leakage power dissipation gets worse as gates get smaller, because gate dielectric thicknesses must proportionately decrease
Nuclear reactor

W / cm2

Pentium II Pentium i386 i486

Pentium 4

Core DUO

Pentium III
Pentium Pro
Adapted from F. Pollack (MICRO99)

Technology from older to newer (m)

31

The Power Wall

Power dissipation in clocked digital devices is related to the clock frequency and feature length imposing a natural limit on clock rates

Significant increase in clock speed without heroic (and expensive) cooling is not possible. Chips would simply melt

Clock speed increased by a factor of 4,000 in less than two decades

The ability of manufacturers to dissipate heat is limited though Look back at the last five years, the clock rates are pretty much flat

Problem might be addressed one day by a Materials Science breakthrough

32

Trivia

AMD Phenom II X4 955 (4 core load)

236 Watts

Intel Core i7 920 (8 thread load)

213 Watts

Human Brain

20 W Represents 2% of our mass Burns 20% of all energy in the body at rest

33

Conventional Wisdom (CW) in Computer Architecture

Old CW: Power is free, Transistors expensive New CW: Power expensive, Transistors free (Can put more on chip than can afford to turn on) Old: Multiplies are slow, Memory access is fast New: Memory slow, multiplies fast [Memory wall] (200-600 clocks to DRAM memory, 4 clocks for FP multiply) Old : Increasing Instruction Level Parallelism via compilers, innovation (Out-oforder, speculation, VLIW, ) New CW: ILP wall diminishing returns on more ILP New: Power Wall + Memory Wall + ILP Wall = Brick Wall

Old CW: Uniprocessor performance 2X / 1.5 yrs New CW: Uniprocessor performance only 2X / 5 yrs?
34

Credit: D. Patterson, UC-Berkeley

Intels Perspective

Intels Platform 2015 documentation, see

http://download.intel.com/technology/computing/archinnov/platform2015/download/RMS.pdf

First of all, as chip geometries shrink and clock frequencies rise, the transistor leakage current increases, leading to excess power consumption and heat. [] Secondly, the advantages of higher clock speeds are in part negated by memory latency, since memory access times have not been able to keep pace with increasing clock frequencies. [] Third, for certain applications, traditional serial architectures are becoming less efficient as processors get faster further undercutting any gains that frequency increases might otherwise buy.

35

OK. Now what?

36

Moores Law

1965 paper: Doubling of the number of transistors on integrated circuits every two years

Moore himself wrote only about the density of components (or transistors) at minimum cost

Increase in transistor count is also a rough measure of computer processing performance

Moore quote: Moore's law has been the name given to everything that changes exponentially. I say, if Gore invented the Internet, I invented the exponential

http://news.cnet.com/Images-Moores-Law-turns-40/2009-1041_3-5649019.html

37

Moores Law (1965)

The complexity for minimum component costs has increased at a rate of roughly a factor of two per year (see graph on next page). Certainly over the short term this rate can be expected to continue, if not to increase. Over the longer term, the rate of increase is a bit more uncertain, although there is no reason to believe it will not remain nearly constant for at least 10 years. That means by 1975, the number of components per integrated circuit for minimum cost will be 65,000. I believe that such a large circuit can be built on a single wafer.

Cramming more components onto integrated circuits by Gordon E. Moore, Electronics, Volume 38, Number 8, April 19, 1965

38

The Ox vs. Chickens Analogy

Seymour Cray: "If you were plowing a field, which would you rather use: Two strong oxen or 1024 chickens?"

Chicken is gaining momentum nowadays:

For certain classes of applications, you can run many cores at lower frequency and come ahead at the speed game

Example: Scenario One: one-core processor w/ power budget W

Increase frequency by 20%

Substantially increases power, by more than 50% But, only increase performance by 13%

Scenario Two: Decrease frequency by 20% with a simpler core

Decreases power by 50% Can now add another dumb core (one more chicken)

39

Micro2015: Evolving Processor Architecture, Intel Developer Forum, March 2005

Intels Vision: Evolutionary Configurable Architecture

Scalar plus many core for highly threaded workloads Many-core array CMP with 10s-100s low power cores Scalar cores Capable of TFLOPS+ Full System-on-Chip Servers, workstations, embedded

Large, Scalar cores for high single-thread performance

Multi-core array CMP with ~10 cores

Dual core Symmetric multithreading

Presentation Paul Petersen, Sr. Principal Engineer, Intel

CMP = chip multi-processor

40

Vision of the Future

Performance

Growing gap!

ISV: Independent Software Vendors

GHz Era

Multi-core Era Time

Parallelism for Everyone Parallelism changes the game A large percentage of people who provide applications are going to have to care about parallelism in order to match the capabilities of their competitors.
competitive pressures = demand for parallel applications
Presentation Paul Petersen, Sr. Principal Engineer, Intel

41

Intel Larrabee and Knights Ferris

Paul Otellini, President and CEO, Intel

"We are dedicating all of our future product development to multicore designs" "We believe this is a key inflection point for the industry."

Larrabee a thing of the past now. Knights Ferry and Intels MIC (Many Integrated Core) architecture with 32 cores for now. Public announcement: May 31, 2010. Commercial release at end of 2012.

42