TY - GEN
T1 - Extracting critical path graphs from MPI applications
AU - Schulz, Martin
PY - 2005
Y1 - 2005
N2 - The critical path is one of the fundamental runtime characteristics of a parallel program. It identifies the longest execution sequence without wait delays. In other words, the critical path is the global execution path that inflicts wait operations on other nodes without itself being stalled. Hence, it dictates the overall runtime and knowing it is important to understand an application's runtime and message behavior and to target optimizations. We have developed a toolset that identifies the critical path of MPI applications, extracts it, and then produces a graphical representation of the corresponding program execution graph to visualize it. To implement this, we intercept all MPI library calls, use the information to build the relevant subset of the execution graph, and then extract the critical path from there. We have applied our technique to several scientific benchmarks and successfully produced critical path diagrams for applications running on up to 128 processors.
AB - The critical path is one of the fundamental runtime characteristics of a parallel program. It identifies the longest execution sequence without wait delays. In other words, the critical path is the global execution path that inflicts wait operations on other nodes without itself being stalled. Hence, it dictates the overall runtime and knowing it is important to understand an application's runtime and message behavior and to target optimizations. We have developed a toolset that identifies the critical path of MPI applications, extracts it, and then produces a graphical representation of the corresponding program execution graph to visualize it. To implement this, we intercept all MPI library calls, use the information to build the relevant subset of the execution graph, and then extract the critical path from there. We have applied our technique to several scientific benchmarks and successfully produced critical path diagrams for applications running on up to 128 processors.
UR - http://www.scopus.com/inward/record.url?scp=50149093347&partnerID=8YFLogxK
U2 - 10.1109/CLUSTR.2005.347035
DO - 10.1109/CLUSTR.2005.347035
M3 - Conference contribution
AN - SCOPUS:50149093347
SN - 0780394852
SN - 9780780394858
T3 - Proceedings - IEEE International Conference on Cluster Computing, ICCC
BT - 2005 IEEE International Conference on Cluster Computing, CLUSTER
T2 - 2005 IEEE International Conference on Cluster Computing, CLUSTER
Y2 - 27 September 2005 through 30 September 2005
ER -