White Paper: Why Performance Management?
Hello, Guest | Login | Register

HPC Hopscotch

Data locality is the key to efficient code.

In my last column, I discussed a possible future for HPC programming. Briefly, I assumed that as cores per socket continue to grow, HPC programming models would diverge. I assume a small thread-based model would be used on multi-core systems (single memory domain) and a large model based on the current message passing (MPI) methodology used in clusters. It seems that I was not alone in thinking about this issue.

Joe Landman over at Scalability.org wrote about The coming bi(tri?)furcation in HPC, part 1 and John Leidel at InsideHPC.com even enshrined my name in his The Eadline Split: The Growing Chasm of Multicore Programming. I believe it is a discussion worth continuing. In the past, I have talked about the goodness that is MPI and at the same time I find it a bit low level for most programmers. Some may even call it…

Please log in to view this content.

Not Yet a Member?

Register with LinuxMagazine.com and get free access to the entire archive, including:

  • Hands-on Content
  • White Papers
  • Community Features
  • And more.
Already a Member?
Log in!


Remember me

Forgotten your password?
Forgotten your username?
Read More
  1. The State of Oracle/Sun Grid Engine
  2. A Cluster In Your Pocket
  3. Moving HPC Closer to The Desktop
  4. Cluster In The Clouds
  5. Summer Language Seminar: The R Project
Follow linuxdlsazine