X10 an object oriented approach to non uniform cluster computing
1 / 24

- PowerPoint PPT Presentation

  • Uploaded on

X10: An Object-Oriented Approach to Non-uniform Cluster Computing. Vijay Saraswat IBM Research. Overview. Introduction and context Clustered Computing Language model and constructs Big picture places, atomic, async, finish, clocks, arrays Example programs and demo

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about '' - tariana

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
X10 an object oriented approach to non uniform cluster computing l.jpg

X10: An Object-Oriented Approach to Non-uniform Cluster Computing

Vijay Saraswat

IBM Research

Overview l.jpg
Overview Computing

  • Introduction and context

    • Clustered Computing

  • Language model and constructs

    • Big picture

    • places, atomic, async, finish, clocks, arrays

  • Example programs and demo

  • Conclusion and Future Work

    • Guarantees

    • Challenges

IBM PL Day 2005

Acknowledgements l.jpg

X10 Tools Computing

Julian Dolby, Steve Fink, Robert Fuhrer, Matthias Hauswirth, Peter Sweeney, Frank Tip, Mandana Vaziri

University partners:

MIT (StreamIt), Purdue University (X10), UC Berkeley (StreamBit), U. Delaware (Atomic sections), U. Illinois (Fortran plug-in), Vanderbilt University (Productivity metrics), DePaul U (Semantics)

X10 core team

Philippe Charles

Chris Donawa (IBM Toronto)

Kemal Ebcioglu

Christian Grothoff (Purdue)

Allan Kielstra (IBM Toronto)

Maged Michael

Christoph von Praun

Vivek Sarkar

Additional contributors to X10 ideas:

David Bacon, Bob Blainey, Perry Cheng, Julian Dolby, Guang Gao (U Delaware), Robert O'Callahan, Filip Pizlo (Purdue), Lawrence Rauchwerger (Texas A&M), Mandana Vaziri, Jan Vitek (Purdue), V.T. Rajan, Radha Jagadeesan (DePaul)


X10 PM+Tools Team Lead:

Kemal Ebcioglu, Vivek Sarkar

PERCS Principal Investigator:

Mootaz Elnozahy

Performance and productivity challenges l.jpg

. . . Computing

Proc Cluster

Proc Cluster

. . .

. . .


L1 $


L1 $


L1 $


L1 $

. . .

L2 Cache

L2 Cache

. . .


. . .

L3 Cache

Performance and Productivity Challenges

2) Frequency wall:Architectures introduce hierarchical heterogeneous parallelism to compensate for frequency scaling slowdown

1) Memory wall:Architectures exhibit severe non-uniformities in bandwidth & latency in memory hierarchy

3) Scalability wall:Software will need to deliver ~ 105-way parallelism to utilize peta-scale parallel systems

IBM PL Day 2005

High complexity limits development productivity l.jpg

Proc Cluster Computing

Proc Cluster

. . .

. . .


L1 $


L1 $


L1 $


L1 $

L2 Cache

L2 Cache

L3 Cache

High Complexity Limits Development Productivity

One billion transistors in a chip

1995: entire chip can be accessed in 1 cycle

. . .

2010: only small fraction of chip can be accessed in 1 cycle

. . .

Major sources of complexity for application developer:

1) Severe non-uniformities in data accesses

2) Applications must exhibit large degrees of parallelism

(up to ~ 105 threads)


. . .

Complexity leads to increases in all phases of HPC Software Lifecycle related to parallel code




Development of Parallel Source Code ---

Design, Code,

Test, Port,

Scale, Optimize


Runs of

Parallel Code

Maintenance and

Porting of Parallel Code







Input Data

Source Code

HPC Software Lifecycle

Percs programming model tools overall architecture l.jpg

Java components Computing

X10 Components

Java runtime

X10 runtime

PERCS Programming Model/Tools: Overall Architecture


Java+Threads+Conc utils

X10 source code

C/C++ /MPI /OpenMP

. . .



Java Development Toolkit

X10 Development Toolkit

C Development Toolkit

Fortran Development Toolkit

. . .

Productivity Metrics

Integrated Programming Environment: Edit, Compile, Debug, Visualize, Refactor

Use Eclipse platform (eclipse.org) as foundation for integrating tools

Morphogenic Software: separation of concerns, separation of roles

Fortran components

C/C++ components

Fast extern


C/C++ runtime

Fortran runtime

Integrated Concurrency Library: messages, synchronization, threads

PERCS = Productive

Easy-to-use Reliable

Computer Systems

Continuous Program Optimization (CPO)

PERCS System Software (K42)

PERCS System Hardware

X10 design assumptions l.jpg

Scalability Computing

Axiom: Programmer must have explicit language constructs to deal with non-uniformity of access.

Axiom: Allow specification of a large collection of activities.

Axiom: A program must use scalable synchronization constructs.

Axiom: The runtime may implement aggregate operations more efficiently than user-specified iterations with index variables.

Axiom: The user may know more than the compiler/RTS.


Axiom: OO provides proven baseline productivity, maintenance, portability benefits.

Axiom: Design must rule out large classes of errors (Type safe, Memory safe, Pointer safe, Lock safe, Clock safe …)

Axiom: Design must support incremental introduction of explicit place types/remote operations.

Axiom: PM must integrate with static tools (Eclipse) -- flag performance problems, refactor code, detect races.

Axiom: PM must support automatic static and dynamic optimization (CPO).

X10 Design Assumptions

Support High Productivity (&, possibly U ) High Performance Programmer

The x10 programming model l.jpg

heap Computing












The X10 Programming Model



Outbound activities

Inbound activities

Partitioned Global heap

Partitioned Global heap

Place-local heap

Place-local heap

Granularity of place can range from single register file to an entire SMP system

. . .

Activities &

Activity-local storage

Activities &

Activity-local storage

. . .

. . .

Inbound activity replies

Outbound activity


Immutable Data

  • A program is a collection of places, each containing resident dataand a dynamic collection of activities.

  • Program may distribute aggregate data (arrays) across places during allocation.

  • Program may directly operate only on local data, using atomic blocks.

  • Program may spawn multiple (local or remote) activities in parallel.

  • Program must use asynchronous operations to access/update remote data.

  • Program may detect termination or (repeatedly) detect quiescence of a data-dependent, distributed set of activities.

async, {at/for}each



atomic, when

finish, clock

Cluster Computing: Common framework for P>=1

Shared Memory (P=1)

MPI (P > 1)

Formalized in Saraswat, Jagadeesan “Concurrent Clustered Programming”.

Async l.jpg

async (P) S Computing

Parent activity creates a new child activity at place P, to execute statement S; returns immediately.

Smay reference final variables in enclosing blocks.


async PlaceExpressionSingleListopt Statement

  • double A[D]=…; // Global dist. array

  • final int k = …;

  • async ( A.distribution[99] ) {

  • // Executed at A[99]’s place

  • atomic A[99] = k;

  • }

cf Cilk’s spawn

IBM PL Day 2005

Finish l.jpg

finish S Computing

Execute S, but wait until all (transitively) spawned async’s have terminated.

Trap all exceptions thrown by spawned activities.

Throw an (aggregate) exception if any spawned async terminates abruptly.

Useful for expressing “synchronous” operations on remote data

And potentially, ordering information in a weakly consistent memory model


Statement ::= finish Statement

finish ateach(point [i]:A) A[i] = i;

finish async(A.distribution[j]) A[j] = 2;

// All A[i]=i will complete before A[j]=2;

finish ateach(point [i]:A) A[i] = i;

finish async(A.distribution[j]) A[j] = 2;

// All A[i]=i will complete before A[j]=2;

cf Cilk’s sync

Rooted Exception Model

Atomic l.jpg

Atomic blocks are Computing

Conceptually executed in a single step, while other activities are suspended

An atomic block may not include

Blocking operations

Accesses to data at remote places

Creation of activities at remote places


Statement ::= atomicStatement

MethodModifier ::= atomic

// target defined in lexically enclosing environment.

public atomic boolean CAS( Object old,

Object new) {

if (target.equals(old)) {

target = new;

return true;


return false;


// push data onto concurrent list-stackNode<int> node=new Node<int>(17);atomic { node.next = head; head = node; }

IBM PL Day 2005

Slide12 l.jpg

Activity suspends until a state in which the guard is true; in that state the body is executed atomically.


Statement ::= WhenStatement

WhenStatement ::=when (Expression)Statement

class OneBuffer {

nullable Object datum = null;

boolean filled = false;


void send(Object v) {

when ( !filled ) {

this.datum = v;

this.filled = true;




Object receive() {

when ( filled ) {

Object v = datum;

datum = null;

filled = false;

return v;




IBM PL Day 2005

Regions distributions l.jpg
regions, distributions in that state the body is executed atomically.

  • Region

    • a (multi-dimensional) set of indices

  • Distribution

    • A mapping from indices to places

  • High level algebraic operations are provided on regions and distributions

region R = 0:100;

region R1 = [0:100, 0:200];

region RInner = [1:99, 1:199];

// a local distribution

distribution D1=R-> here;

// a blocked distribution

distribution D = block(R);

// union of two distributions

distribution D = (0:1) -> P0 || (2:N) -> P1;

distribution DBoundary = D – RInner;

Based on ZPL.

IBM PL Day 2005

Arrays l.jpg

Array section in that state the body is executed atomically.

A [RInner]

High level parallel array, reduction and span operators

Highly parallel library implementation

A-B (array subtraction)



Arrays may be



Value types

Initialized in parallel:

int [D] A= new int[D] (point [i,j]) {return N*i+j;};


IBM PL Day 2005

Ateach foreach l.jpg

ateach (point p:A) S in that state the body is executed atomically.

Creates|region(A)|async statements

Instancepof statementSis executed at the place where A[p]is located

foreach (point p:R) S

Creates|R|async statements in parallel at current place

Termination of all activities can be ensured using finish.

ateach, foreach

ateach ( FormalParam: Expression )Statement

foreach ( FormalParam: Expression )Statement

public boolean run() {

distribution D = distribution.factory.block(TABLE_SIZE);

long[.] table = new long[D] (point [i]) { return i; }

long[.] RanStarts = new long[distribution.factory.unique()]

(point [i]) { return starts(i);};

long[.] SmallTable = new long value[TABLE_SIZE]

(point [i]) {return i*S_TABLE_INIT;};

finish ateach (point [i] : RanStarts ) {

long ran = nextRandom(RanStarts[i]);

for (int count: 1:N_UPDATES_PER_PLACE) {

int J = f(ran);

long K = SmallTable[g(ran)];

async atomic table[J] ^= K;

ran = nextRandom(ran);


return table.sum() == EXPECTED_RESULT;


IBM PL Day 2005

Clocks l.jpg

Operations in that state the body is executed atomically.

clock c = new clock();


Signals completion of work by activity in this clock phase.


Blocks until all clocks it is registered on can advance. Implicitly resumes all clocks.


Unregister activity with c.

async (P) clock (c1,…,cn)S

(Clocked async): activity is registered on the clocks (c1,…,cn)

Static Semantics

An activity may operate only on those clocks it is live on.

In finish S,Smay not contain any top-level clocked asyncs.

Dynamic Semantics

A clock c can advance only when all its registered activities have executed c.resume().


No explicit operation to register a clock.

Supports over-sampling, hierarchical nesting.

IBM PL Day 2005

Example specjbb l.jpg
Example: SpecJBB in that state the body is executed atomically.

finish async {

clock c = new clock();

Company company = createCompany(...);

for (int w : 0:wh_num) for (int t: 0:term_num)

async clocked(c) { // a client


next; //1.

while (company.mode!=STOP) {

select a transaction;


process the transaction;

if (company.mode==RECORDING)

record data;

if (company.mode==RAMP_DOWN) {

c.resume(); //2.



gather global data;

} // a client

// master activity

next; //1.

company.mode = RAMP_UP;

sleep rampuptime;

company.mode = RECORDING;

sleep recordingtime;

company.mode = RAMP_DOWN;

next; //2.

// All clients in RAMP_DOWN

company.mode = STOP;

} // finish

// Simulation completed.

print results.

IBM PL Day 2005

Formal semantics fx10 l.jpg

Based on Middleweight Java (MJ) in that state the body is executed atomically.

Configuration is a tree of located processes

Tree necessary for finish.

Clocks formalized using short circuits (PODC 88).

Bisimulation semantics.

Basic theorems

Equational laws

Clock quiescence is stable.

Monotonicity of places.

Deadlock freedom (for language w/out when).

… Type Safety

… Memory Safety

Formal semantics (FX10)

Current status l.jpg

We have an operational X10 0.41 implementation in that state the body is executed atomically.

All programs shown here run.

Current Status


PERCS Kickoff


X10 Kickoff


Code Templates

X10 0.32 Spec Draft

X10 Multithreaded RTS

X10 Grammar

Annotated AST

Target Java

Native code


Analysis passes


Code emitter



X10 source

X10 Prototype #1

PEM Events

  • Code metrics

    • Parser: ~45/14K*

    • Translator: ~112/9K

    • RTS: ~190/10K

    • Polyglot base: ~517/80K

    • Approx 180 test cases.

    • (* classes+interfaces/LOC)

Program output

  • Structure

    • Translator based on Polyglot (Java compiler framework)

    • X10 extensions are modular.

    • Uses Jikes parser generator.

  • Limitations

    • Clocked final not yet implemented.

    • Type-checking incomplete.

    • No type inference.

    • Implicit syntax not supported.


X10 ProductivityStudy


X10 Prototype #2


Open Source Release?

IBM PL Day 2005

Future work implementation l.jpg

Type checking/inference in that state the body is executed atomically.

Clocked types

Place-aware types

Consistency management

Lock assignment for atomic sections

Data-race detection

Activity aggregation

Batch activities into a single thread.

Message aggregation

Batch “small” messages.


Dynamic, adaptive migration of places from one processor to another.

Continuous optimization

Efficient implementation of scan/reduce

Efficient invocation of components in foreign languages

C, Fortran

Garbage collection across multiple places

Future Work: Implementation

Welcome University Partners and other collaborators.

IBM PL Day 2005

Future work other topics l.jpg

Design/Theory in that state the body is executed atomically.

Atomic blocks

Structural study of concurrency and distribution

Clocked types

Hierarchical places

Weak memory model

Persistence/Fault tolerance

Database integration


Refactoring language.


Several HPC programs planned currently.

Also: web-based applications.

Future work: Other topics

Welcome University Partners and other collaborators.

IBM PL Day 2005

Backup material l.jpg

Backup material in that state the body is executed atomically.

Type system l.jpg

Value classes in that state the body is executed atomically.

May only have final fields.

May only be subclassed by value classes.

Instances of value classes can be copied freely between places.

nullable is a type constructor

nullable T contains the values of T and null.

Place types: [email protected], specify the place at which the data object lives.

Type system

Future work: Include generics and dependent types.

IBM PL Day 2005

Example latch l.jpg
Example: Latch in that state the body is executed atomically.

public class Latch implements future {

protected boolean forced = false;

protected nullable boxed result = null;

protected nullable exception z = null;

public atomic

boolean setValue( nullable Object val,

nullable exception z ) {

if ( forced ) return false;

// these assignment happens only once.

this.result .val= val;

this.z = z;

this.forced = true;

return true;

public atomic boolean forced() {

return forced;


public Object force() {

when ( forced ) {

if (z != null) throw z;

return result;




public interface future {

boolean forced();

Object force();


public class boxed {

nullable Object val;


IBM PL Day 2005