~/talk

Identifying Performance Changes Using Peass

Talkat FOSDEM 2021 · on Sunday, 2021-02-07· at 17:25· D.cicd· [testing, devops-and-delivery]

speaker

name:David Georg Reichelt
links:none on file

resources

video:https://video.fosdem.org/2021/D.cicd/identifying_performance_changes_using_peass.mp4
slides:https://fosdem.org/2021/schedule/event/identifying_performance_changes_using_peass/attachments/slides/4681/export/events/attachments/identifying_performance_changes_using_peass/slides/4681/Peass_slides_fosdem.pdf

summary

Describes Peass, a tool that converts existing unit tests into performance tests and integrates with Jenkins via Peass-CI to run them in CI. Covers three prototype steps: regression test selection that compares execution traces and called-source to prune unaffected tests, a measurement protocol that restarts the JVM and repeats iterations until statistical detection of performance changes, and a root-cause analysis that locates the call-tree node responsible for a detected change. Finishes with a live demonstration of Peass running in Jenkins.

AI-written summary · about

related talks

~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.