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

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.Comment: In Proceedings FESCA 2013, arXiv:1302.478

A Tool for Optimizing the Build Performance of Large Software Code Bases

We present Build Analyzer, a tool that helps developers optimize the build performance of huge systems written in C. Due to complex C header dependencies, even small code changes can cause extremely long rebuilds, which are problematic when code is shared and modified by teams of hundreds of individuals. Build Analyzer supports several use cases. For developers, it provides an estimate of the build impact and distribution caused by a given change. For architects, it shows why a build is costly, how its cost is spread over the entire code base, which headers cause build bottlenecks, and suggests ways to refactor these to reduce the cost. We demonstrate Build Analyzer with a use-case on a real industry code base.

Analsis Performansi Refactoring Database

ABSTRAKSI: Refactoring Database merupakan proses memperbaiki desain dari suatu skema basis data dengan memperhatikan faktor-faktor tertentu yang disebut dengan database smell. Perubahan desain dari skema database akan mempengaruhi waktu pemrosesan query dan biaya pemrosesan query. Dengan menggunakan pada sebuah representasi lojik, yaitu entity relationship diagram (ERD), dibuat desain dari suatu skema basis data yang telah di-refactor. Dalam menyelesaikan pemrosesan query pada proses bisnis yang telah ditentukan, skema refactoring dapat menyelesaikan semua pemrosesan query walaupun bila dibandingkan dari sudut pandang waktu pemrosesan query dengan skema yang tidak mengalami refactoring, tidak berbanding jauh. Namun terlihat bahwa terdapat kasus-kasus dimana biaya untuk pemrosesan query dapat diproses dengan biaya yang murah bila menggunakan skema refactoring.Kata Kunci : Refactoring, skema basis data, queryABSTRACT: Database Refactoring is a process to improve design of a database schema by observing some factors called database smells. Design changes of a database schema will affect processing time and cost for processing the query itself. Using a logic representation, which is entity relationship diagram (ERD), a design is made from a database schema that has been refactored. In compeleting query processing on a choosen bussines process, refactored schema can done all the query processing although if compared to schema without refactoring from query processing point of view, the result is not far difference. But proven that there is some case where the cost for query processing can be reduced using refactored schema.Keyword: Refactoring, database schema, quer