Note that there are some explanatory texts on larger screens.

plurals
  1. PODetecting and pinpointing performance regressions
    text
    copied!<p>Are there any known techniques (and resources related to them, like research papers or blog entries) which describe how do dynamically <strong>programatically</strong> detect the part of the code that caused a performance regression, and if possible, on the JVM or some other virtual machine environment (where techniques such as instrumentation can be applied relatively easy)?</p> <p>In particular, when having a large codebase and a bigger number of committers to a project (like, for example, an OS, language or some framework), it is sometimes hard to find out the change that caused a performance regression. A paper such as <a href="http://buytaert.net/statistically-rigorous-java-performance-evaluation" rel="nofollow">this one</a> goes a long way in describing how to <strong>detect</strong> performance regressions (e.g. in a certain snippet of code), but not how to dynamically <strong>find</strong> the piece of the code in the project that got changed by some commit and caused the performance regression.</p> <p>I was thinking that this might be done by instrumenting pieces of the program to detect the exact method which causes the regression, or at least narrowing the range of possible causes of the performance regression.</p> <p>Does anyone know about anything written about this, or any project using such performance regression detection techniques?</p> <p>EDIT:</p> <p>I was referring to something along <a href="http://www.phoronix.com/scan.php?page=article&amp;item=linux_perf_regressions&amp;num=2" rel="nofollow">these lines</a>, but doing further analysis into the codebase itself.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload