Software model refactoring based on performance analysis: better working on software or performance side?

TL;DR

This paper compares two methods for interpreting model-based performance analysis results—performance antipattern detection and bidirectional model transformations—highlighting their differences and discussing the advantages of working on software versus performance models.

Contribution

It introduces and compares two novel approaches for translating performance analysis results into architectural feedback, analyzing their effectiveness and trade-offs.

Findings

Performance antipattern detection provides specific architectural insights.

Bidirectional model transformations enable flexible interpretation of models.

Working on the software side offers different benefits compared to the performance side.

Abstract

Several approaches have been introduced in the last few years to tackle the problem of interpreting model-based performance analysis results and translating them into architectural feedback. Typically the interpretation can take place by browsing either the software model or the performance model. In this paper, we compare two approaches that we have recently introduced for this goal: one based on the detection and solution of performance antipatterns, and another one based on bidirectional model transformations between software and performance models. We apply both approaches to the same example in order to illustrate the differences in the obtained performance results. Thereafter, we raise the level of abstraction and we discuss the pros and cons of working on the software side and on the performance side.