Leveraging performance counters and execution logs to diagnose memory-related performance issues

Authors: Mark D. Syer Zhen Ming Jiang Meiyappan Nagappan Ahmed E. Hassan Mohamed Nasser Parminder Flora

Venue: ICSME   2013 IEEE International Conference on Software Maintenance, pp. 110--119, 2013

Year: 2013

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 performance 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%.

Preprint: PDF

BibTeX:

@inproceedings{markd.syer2013lpcaeltdmpi,
    author = "Mark D. Syer and Zhen Ming Jiang and Meiyappan Nagappan and Ahmed E. Hassan and Mohamed Nasser and Parminder Flora",
    title = "Leveraging performance counters and execution logs to diagnose memory-related performance issues",
    year = "2013",
    pages = "110--119",
    booktitle = "Proc. of 2013 IEEE International Conference on Software Maintenance"
}

Plain Text:

Mark D. Syer, Zhen Ming Jiang, Meiyappan Nagappan, Ahmed E. Hassan, Mohamed Nasser, and Parminder Flora, "Leveraging performance counters and execution logs to diagnose memory-related performance issues," 2013 IEEE International Conference on Software Maintenance, pp. 110--119