~/talk

GPUIterator: Bridging the Gap between Chapel and GPU Platforms

Talkat CHIUW 2019 · on Saturday, 2019-06-22
links:none on file
links:none on file
links:none on file
slides:none on file

A Chapel module called GPUIterator module implements a portable interface to run Chapel forall loops on GPUs (CUDA and OpenCL), accept distributed domains across CPU+GPU nodes, and split iterations by a tunable percentage for hybrid CPU+GPU partitioning. It requires only ~6–11 lines changed in Chapel user code (versus ~50–100 lines for raw CUDA/OpenCL), wires to hand-tuned native kernels, is open source, and shows up to ~14× multi-node speedup and about ≈55% gain from hybrid execution when CPU and GPU performance are comparable.

AI-written summary · about

  1. 0:00Introduction
  2. 1:29CPU Programming
  3. 3:15CPU Code
  4. 4:04Switching between versions
  5. 5:57CPU integrator
  6. 7:51JP
  7. 12:20Twitter
  8. 12:52Generator
  9. 13:46Implementation
  10. 15:06CPU Support
  11. 16:15Performance Simulation
  12. 17:03CPU
  13. 17:52Line Count
  14. 18:55Xaxis
  15. 23:05Application Graph
  16. 24:40Final Thoughts
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.