Dynamic analysis of java applications for multithreaded antipatterns

Boroday, Sergiy; Petrenko, Alexandre; Singh, Jashanjot; Hallal, H.

doi:10.1145/1082983.1083247

Cited by 9 publications

(4 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Contrary to design patterns, antipatterns describe what not to do. There exist general antipatterns [3] and antipatterns specific to concurrent processes [46], J2EE [47], [48], performance [49], XML [48], and other sub-fields of software engineering.…”

Section: ) Running Examplementioning

confidence: 99%

DECOR: A Method for the Specification and Detection of Code and Design Smells

Moha

Guéhéneuc

Duchien

et al. 2010

IIEEE Trans. Software Eng.

671

505

View full text Add to dashboard Cite

Abstract-Code and design smells are poor solutions to recurring implementation and design problems. They may hinder the evolution of a system by making it hard for software engineers to carry out changes. We propose three contributions to the research field related to code and design smells: (1) DECOR, a method that embodies and defines all the steps necessary for the specification and detection of code and design smells; (2) DETEX, a detection technique that instantiates this method; and (3) an empirical validation in terms of precision and recall of DETEX. The originality of DETEX stems from the ability for software engineers to specify smells at a high-level of abstraction using a consistent vocabulary and domain-specific language for automatically generating detection algorithms. Using DETEX, we specify four well-known design smells: the antipatterns Blob, Functional Decomposition, Spaghetti Code, and Swiss Army Knife, and their 15 underlying code smells, and we automatically generate their detection algorithms. We apply and validate the detection algorithms in terms of precision and recall on XERCES v2.7.0, and discuss the precision of these algorithms on 11 opensource systems.

show abstract

Section: ) Running Examplementioning

confidence: 99%

DECOR: A Method for the Specification and Detection of Code and Design Smells

Moha

Guéhéneuc

Duchien

et al. 2010

IIEEE Trans. Software Eng.

671

505

View full text Add to dashboard Cite

show abstract

“…(s) Spin Wait Busy Waiting (Boroday et al, 2005) The Spin Wait anti-pattern describes the problem of actively waiting for a condition (i.e. repeatedly checking the condition).…”

Section: Name Referencementioning

confidence: 99%

Performance problem diagnostics by systematic experimentation

Wert

2013

Proceedings of the 18th International Doctoral Symposium on Components and Architecture

View full text Add to dashboard Cite

The performance of enterprise software systems has a direct impact on the success of business. Recent studies have shown that software performance affects customer satisfaction as well as operational costs of software. Hence, software performance constitutes an essential competitive and differentiating factor for software vendors and operators. In industrial practice, it is still a challenging task to detect software performance problems before they are faced by end users. Diagnostics of performance problems requires deep expertise in performance engineering and still entails a high manual effort. As a consequence, performance evaluations are postponed to the last minute of the development process, or even are completely omitted. Instead of proactively avoiding performance problems, problems are fixed in a reactive manner when they first emerge in operations. Since reactive, operation-time resolution of performance problems is very expensive and has a negative impact on the reputation of software vendors, performance problems need to be diagnosed and resolved in the process of software development. Existing approaches addressing performance problem diagnostics either assume the existence of a performance model, are limited to problem detection without analyzing root causes, or are applied as reactive approaches during the operations phase and, thus, cannot be effective applied during development for performance problem diagnostics.In this thesis, we introduce an automatic, experiment-based approach for performance problem diagnostics in enterprise software systems. We describe a method to derive a taxonomy on recurrent types of performance problems and introduce a systematic experimentation concept. Using the taxonomy as a search tree, the proposed approach systematically searches for root causes of detected performance problems by executing series of systematic performance experiments. Based on the measurement data from experiments, detection heuristics decide on the presence of performance problems in the target system. Furthermore, we develop a domain-specific description language to specify the information required for automatic performance problem diagnostics. Finally, we create and evaluate a representative set of detection heuristics. We validate our approach by means of five studies including end-to-end case studies, a controlled experiment and an empirical study. The results of the validation show that our approach is applicable to a wide range of contexts and is able to fully automatically and accurately detect performance problems in medium-size and large-scale applications. External users of the provided approach evaluated it as a useful support for diagnostics of performance problems and exposed their willingness to use the approach for their own software development projects. Explicitly designed for automatic, development-time testing, our approach can be incorporated into continuous integration. In this way, our approach allows regular, automatic diagnostics of performance problems involving minima...

show abstract

“…For example, in [15] data-flow antipatterns help to discover errors in workflows and are formalized through the CTL* temporal logic. As another example, in [16] antipatterns help to discover multi threading problems of java applications and are specified through the LTL temporal logic.…”

Section: Related Workmentioning

confidence: 99%

Performance Antipatterns as Logical Predicates

Cortellessa

Marco²,

Trubiani

2010

2010 15th IEEE International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

The problem of interpreting the results of performance analysis is quite critical in the software performance domain. Mean values, variances, probability distributions are hard to interpret for providing feedback to software architects. Instead, what architects expect are solutions to performance problems, possibly in the form of architectural alternatives (e.g. split a software component in two components and re-deploy one of them). In a software performance engineering approach this path from analysis results to software alternatives still lacks of automation and is based on the skills and experience of analysts. In this paper we propose an automated approach for the performance feedback generation process based on performance antipatterns. To this aim, we model performance antipatterns as logical predicates and we provide a java engine, based on such predicates, that is able to detect performance antipatterns in an XML representation of the software system. Finally, we show the approach at work on a simple case study.

show abstract

Dynamic analysis of java applications for multithreaded antipatterns

Cited by 9 publications

References 22 publications

DECOR: A Method for the Specification and Detection of Code and Design Smells

DECOR: A Method for the Specification and Detection of Code and Design Smells

Performance problem diagnostics by systematic experimentation

Performance Antipatterns as Logical Predicates

Contact Info

Product

Resources

About