Optimizing Aspectual Execution Mechanisms for Embedded Applications

Hundt, Christine; Glesner, Sabine

doi:10.1016/j.entcs.2009.05.005

Cited by 5 publications

(7 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Run-time (Malek et al, 2010) Stylistic ext, avmo ext: -negl, avmo: +1.03x to 1.1x (Zhang, 2009) Synchronization bos negl (Hundt and Glesner, 2009) Maintainability, Extensibility (Ansaloni et al, 2010) Comunication between threads ext + factor up to 31.08x (Ortiz and Prado, 2010) Device adaptation ext negl Compile-time / runtime (Froihofer et al, 2007) Constraint validation ext + varies according to approach Domain Specific (Dyer and Rajan, 2010) Cache met + 1.015x NA (de Roo et al, 2012) Safety NA + NA (Georg et al, 2009) Security ext + varies according to approach sured in factors (when comparable to the original implementation) or percentage. Some cases related this overhead as negligible (negl).…”

Section: Performance Overheadmentioning

confidence: 99%

“…One hypothesis for such lack of large scale studies is that aspectoriented programming is not extensively adopted such as object-oriented programming or procedural programming. Therefore, the low adoption from the Middleware (Malek et al, 2010) 12.3 KSLOC Java AspectJ Generic ext: -negl, avmo: +1.03x to 1.1x (Zhang, 2009) 12.7 KLOC,113Kb,190Kb FlexSync Industrial negl Embedded (Hundt and Glesner, 2009) NA ObjectTeams, Java (Ganesan et al, 2009) AspectJ Office not notably significant Application (Cannon and Wohlstadter, 2009) 46KLOC…”

Section: On the Target Applicationsmentioning

confidence: 99%

“…From the second set of criteria, it is possible to conclude that run-time is the most common weaving type process presented by papers in the experiments. One of the reasons for this choice, instead of compile-time weaving, is the fact that runtime weaving allows aspects to be added to the base program dynamically, which is better for a context-aware adaptation of the applications (Hundt and Glesner, 2009). Some papers not only used the runtime weaving process but also extended it to adequate the process to their studies.…”

Section: On the Type Of Weavingmentioning

confidence: 99%

“…There are different approaches to accomplish aspect weaving (Hundt and Glesner, 2009): Compiletime weaving which weaves the aspect in a static way into the original code, Run-time weaving which weaves the aspect dynamically at runtime, and Loadtime weaving which delays weaving of crosscutting concerns until the class loader loads the class file and defines it to the Virtual Machine (Dyer and Rajan, 2010).…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Systematic Review on Performance Evaluation of Aspect-Oriented Programming Techniques used to Implement Crosscutting Concerns

Silva

Maia

Soares

2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Aspect-Oriented Programming (AOP) was proposed with the main objective of addressing an important software quality principle that is modularization. The basic idea of the paradigm is to capture crosscutting concerns as a programming abstraction called aspect. Since the introduction of aspects as a complement to objectoriented programming, many evaluations and empirical studies were provided to the new paradigm, including the application of a variety of software metrics in order to provide evidence of the benefits or problems with the new paradigm. There is no consensus about the impact on performance of the use of AOP techniques to deal with crosscutting concerns. The use of AOP to implement crosscutting concerns and its impact on performance is the motivation for this study. This paper explores further the evaluation of performance by proposing a systematic literature review with the purpose of finding out how performance is affected by the introduction of aspects. The result of this systematic review is that there has been few studies on scientific literature concerning AOP and performance and most of these studies are too specific, and sometimes even inconclusive. This article presents these miscellaneous results and how they were extracted from the literature.

show abstract

Section: Performance Overheadmentioning

confidence: 99%

Section: On the Target Applicationsmentioning

confidence: 99%

Section: On the Type Of Weavingmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Systematic Review on Performance Evaluation of Aspect-Oriented Programming Techniques used to Implement Crosscutting Concerns

Silva

Maia

Soares

2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…O weaver é a ferramenta que realiza o proesso de weaving. Há diferentes abordagens para se realizar o processo de weaving [Hundt e Glesner 2009]: 1. Compile-time weaving ou Build-time weaving : em tempo de compilação ou build faz a junção do aspecto com o código base.…”

Section: Processo De Weavingunclassified

Avaliação do desempenho de técnicas de programação orientada a aspectos

Silva¹

View full text Add to dashboard Cite

Aspect-Oriented Programming (AOP) was proposed with the main objective of addressing an important software quality principle that is modularization. The basic idea of the paradigm is to capture crosscutting concerns and handle them independently from the rest of the application. AOP emerged as complement to Object-Oriented Programming (OOP), generating many evaluations and empirical studies about this new paradigm. A variety of metrics were applyed on AOP in order to provide evidence of its benets or problems, however there is no consensus about the impact on performance of the use of AOP techniques to deal with crosscutting concerns on systems. In order to identify if these techniques related to AOP have impact on system performance, this study proposed a controlled experiment on an academic system of the Federal University of Uberlândia.The experiment had the purpose of assessing factors related to AOP which may inuence systems performance. According to the results achieved by this study, factors such as the weaver, number of join points, type of advice and number of lines of code (LOC) aect systems performance when it comes to AOP. This inuence, however, showed up to be negligible for common web applications which access databases and have MVC framework. Results also address that, specically for the load-time weaving process, the stage of loading of classes may aect performance of applications which run on the same environment. These results can be used by architects and developers to reason about system architecture projects concerning the use of AOP.

show abstract