Locating Performance Changes in Source Code

In regression benchmarking, it is often complicated to locate the source code modification which caused a performance change detected by a particular benchmark. Manually examining all modifications and resolving if some specific modification has caused the performance change in large projects can be...

Full description

Bibliographic Details
Main Author: Olšák, Libor
Other Authors: Adámek, Jiří
Format: Dissertation
Language:English
Published: 2008
Online Access:http://www.nusl.cz/ntk/nusl-287611
id ndltd-nusl.cz-oai-invenio.nusl.cz-287611
record_format oai_dc
spelling ndltd-nusl.cz-oai-invenio.nusl.cz-2876112017-06-27T04:41:21Z Locating Performance Changes in Source Code Locating Performance Changes in Source Code Adámek, Jiří Olšák, Libor Kalibera, Tomáš In regression benchmarking, it is often complicated to locate the source code modification which caused a performance change detected by a particular benchmark. Manually examining all modifications and resolving if some specific modification has caused the performance change in large projects can be timeconsuming. The thesis analyses possible methods for making that examination faster; focusing in more detail on two of them. The first is to have software that can understand the source language and can resolve which modification can potentially cause performance changes. For example, modifications in comments can not affect performance. The second is selecting source changes that were executed during the test. As a proof of concept, the methods are implemented in Mono Regression Benchmarking Suite. In this master thesis, more solutions how to increase time efficiency of the search are discussed and the two noticed above are implemented. 2008 info:eu-repo/semantics/masterThesis http://www.nusl.cz/ntk/nusl-287611 eng info:eu-repo/semantics/restrictedAccess
collection NDLTD
language English
format Dissertation
sources NDLTD
description In regression benchmarking, it is often complicated to locate the source code modification which caused a performance change detected by a particular benchmark. Manually examining all modifications and resolving if some specific modification has caused the performance change in large projects can be timeconsuming. The thesis analyses possible methods for making that examination faster; focusing in more detail on two of them. The first is to have software that can understand the source language and can resolve which modification can potentially cause performance changes. For example, modifications in comments can not affect performance. The second is selecting source changes that were executed during the test. As a proof of concept, the methods are implemented in Mono Regression Benchmarking Suite. In this master thesis, more solutions how to increase time efficiency of the search are discussed and the two noticed above are implemented.
author2 Adámek, Jiří
author_facet Adámek, Jiří
Olšák, Libor
author Olšák, Libor
spellingShingle Olšák, Libor
Locating Performance Changes in Source Code
author_sort Olšák, Libor
title Locating Performance Changes in Source Code
title_short Locating Performance Changes in Source Code
title_full Locating Performance Changes in Source Code
title_fullStr Locating Performance Changes in Source Code
title_full_unstemmed Locating Performance Changes in Source Code
title_sort locating performance changes in source code
publishDate 2008
url http://www.nusl.cz/ntk/nusl-287611
work_keys_str_mv AT olsaklibor locatingperformancechangesinsourcecode
_version_ 1718469474226536448