Skip to main navigation Skip to search Skip to main content

A visual analytics framework for the detection of anomalous call stack trees in high performance computing applications

  • Stony Brook University
  • Brookhaven National Laboratory

Research output: Contribution to journalArticlepeer-review

47 Scopus citations

Abstract

Anomalous runtime behavior detection is one of the most important tasks for performance diagnosis in High Performance Computing (HPC). Most of the existing methods find anomalous executions based on the properties of individual functions, such as execution time. However, it is insufficient to identify abnormal behavior without taking into account the context of the executions, such as the invocations of children functions and the communications with other HPC nodes. We improve upon the existing anomaly detection approaches by utilizing the call stack structures of the executions, which record rich temporal and contextual information. With our call stack tree (CSTree) representation of the executions, we formulate the anomaly detection problem as finding anomalous tree structures in a call stack forest. The CSTrees are converted to vector representations using our proposed stack2vec embedding. Structural and temporal visualizations of CSTrees are provided to support users in the identification and verification of the anomalies during an active anomaly detection process. Three case studies of real-world HPC applications demonstrate the capabilities of our approach.

Original languageEnglish
Article number8440859
Pages (from-to)215-224
Number of pages10
JournalIEEE Transactions on Visualization and Computer Graphics
Volume25
Issue number1
DOIs
StatePublished - Jan 2019

Keywords

  • Active Learning
  • Anomaly Detection
  • Call Stack
  • Performance Visualization
  • Representation Learning

Fingerprint

Dive into the research topics of 'A visual analytics framework for the detection of anomalous call stack trees in high performance computing applications'. Together they form a unique fingerprint.

Cite this