AIM: Adaptable Instrumentation and Monitoring for Automated Software Performance Analysis

Abstract

Instrumentation and monitoring plays an important role in measurement-based performance analysis of software systems. However, in practice the performance overhead of extensive instrumentation is not negligible. Experiment-based performance analysis overcomes this problem through a series of experiments on selectively instrumented code, but requires additional manual effort to adjust required instrumentation and hence introduces additional costs. Automating the experiments and selective instrumentation can massively reduce the costs of performance analysis. Such automation, however, requires the capability of dynamically adapting instrumentation instructions. In this paper, we address this issue by introducing AIM, a novel instrumentation and monitoring approach for automated software performance analysis. We apply AIM to automate derivation of resource demands for an architectural performance model, showing that adaptable instrumentation leads to more accurate measurements compared to existing monitoring approaches.

Despliegue de monitores con los mecanismos de reflexión y las extensiones de gestión de Java

“…En [4] se presentó la herramienta SPASS-meter, la cual aplica la monitorización en los programas de las plataformas Java y Android, realiza análisis en tiempo de ejecución y presenta los resultados en tiempo real. En [5] se introdujo un marco de trabajo para la monitorización e instrumentación con capacidades de adaptación, dicho marco utiliza la interfaz de herramientas de la máquina virtual de Java (JVM TI por sus siglas en inglés) y los elementos de instrumentación de Java.…”

Process Discovery in Business Process Management Optimization

“…For many years business process management (BPM) approach has been used to analyze business processes in many organizations. Traditional business process management methods assume the following five stages in the business process cycle: Process design consisting of creating a new or changing an existing process model; creating a process instance, its configuration and startup; executing; monitoring the execution of the process instance; and analyzing the performance of the process for improvement [1][2][3].…”

“…In recent years, an essential change in the trend of transaction processing may be observed, as follows: The traditional BPM approach has been replaced with the Case Management one with process discovery methods, which are more and more often associated with the process lifecycle. Such an approach allows the transformation of input data from event logs registered during process execution into process models [1][2][3][4][5][6]. This transformation happens without the existence of any prior information about how the intended process should look.…”

“…This transformation happens without the existence of any prior information about how the intended process should look. The built-in model usually takes the form of a graph, as follows: Petri net, BPMN (Business Process Model and Notation), EPC (Event-driven Process Chain diagram), or UML (Unified Modeling Language) activity diagram [2,3,5]. Process model validation methods consist of a comparison of an existing process model to the actual event log records.…”

“…Methods of extending the process model include the expansion and improvement of the current process model using contextual information on the real implementation of activities registered in the event log. Meanwhile, process model validation evaluates the compatibility of the model with actual process data and the development of the process model is aimed at modifying or enlarging the existing model [1,3,7,8].…”