BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20181221T160727Z
LOCATION:D166
DTSTART;TZID=America/Chicago:20181112T090500
DTEND;TZID=America/Chicago:20181112T100000
UID:submissions.supercomputing.org_SC18_sess173_pec336@linklings.com
SUMMARY:Exascale Challenges in Across-Node Parallelism for Languages and R
 untimes
DESCRIPTION:Workshop\nAccelerators, Exascale, Parallel Programming Languag
 es, Libraries, and Models, Workshop Reg Pass\n\nExascale Challenges in Acr
 oss-Node Parallelism for Languages and Runtimes\n\nKale\n\nMachines with p
 eak performance exceeding one exaflop/s are just around the corner, and pr
 omises of sustained exaflop/s machines abound. Are there significant chall
 enges in runtime frameworks and languages that need to be met to harness t
 he power of these machines?  We will examine this question and associated 
 issues. \n\nThere are some architectural trends that are becoming clear an
 d some hazily appearing. Individual nodes are getting “fatter” computation
 ally. Accelerators such as GPGPUs and possibly FPGAs are likely parts of t
 he exascale landscape. High bandwidth memory, and non-coherent caches (suc
 h as the caches in GPGPUs used typically for constant memory), NVRAMS, and
  resultant deeper and more complex memory hierarchies will also have to be
  dealt with. \n\nThere is an argument going around in the community, that 
 we have already figured out how to deal with tens of thousands of nodes (1
 00,000 with BG/Q), and now since the number of nodes is not likely to incr
 ease, we (the extreme-scale HPC community) have to focus research almost e
 ntirely on within-node issues. I believe this is not quite a well-founded 
 argument. I will explain why issues of power/energy/temperature, whole mac
 hine (multi-job) optimizations, across node issues like communication opti
 mization, load balancing and fault tolerance are still worthy of significa
 nt attention of the exascale runtime and language community. At the same t
 ime, there exist issues in handling within-node parallelism that arise mai
 nly or only in the context large multi-node runs. \n\nI will also address 
 the question of how our community should approach research if a large segm
 ent of funding sources and application community have started thinking som
 e of the above issues are irrelevant. What should the courage of our convi
 ctions lead us to?
URL:https://sc18.supercomputing.org/presentation/?id=pec336&sess=sess173
END:VEVENT
END:VCALENDAR

