DMCA
Leveraging performance counters and execution logs to diagnose memory-related performance issues
| Venue: | in ICSM ’13: Proceedings of the 2013 IEEE International Conference on Software Maintenance, 2013 |
| Citations: | 3 - 0 self |
BibTeX
@INPROCEEDINGS{Syer_leveragingperformance,
author = {Mark D. Syer and Zhen Ming Jiang and Ahmed E. Hassan and Mohamed Nasser and Parminder Flora},
title = {Leveraging performance counters and execution logs to diagnose memory-related performance issues},
booktitle = {in ICSM ’13: Proceedings of the 2013 IEEE International Conference on Software Maintenance, 2013},
year = {},
pages = {110--119}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Abstract—Load tests ensure that software systems are able to perform under the expected workloads. The current state of load test analysis requires significant manual review of performance counters and execution logs, and a high degree of system-specific expertise. In particular, memory-related issues (e.g., memory leaks or spikes), which may degrade performance and cause crashes, are difficult to diagnose. Performance analysts must correlate hundreds of megabytes or gigabytes of performance counters (to understand resource usage) with execution logs (to understand system behaviour). However, little work has been done to combine these two types of information to assist per-formance analysts in their diagnosis. We propose an automated approach that combines performance counters and execution logs to diagnose memory-related issues in load tests. We perform three case studies on two systems: one open-source system and one large-scale enterprise system. Our approach flags ≤0.1 % of the execution logs with a precision ≥80%.
Keyphrases
execution log performance counter memory-related performance issue memory-related issue memory leak significant manual review cause crash resource usage system behaviour load test analysis high degree abstract load test case study performance analyst large-scale enterprise system per-formance analyst expected workload automated approach software system open-source system current state little work system-specific expertise load test
