You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/08 17:08:02 UTC
[jira] [Commented] (BEAM-8199) Improve tooling to enable alerts on
performance regression based on data collected from Beam benchmarks
[ https://issues.apache.org/jira/browse/BEAM-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192334#comment-17192334 ]
Beam JIRA Bot commented on BEAM-8199:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Improve tooling to enable alerts on performance regression based on data collected from Beam benchmarks
> -------------------------------------------------------------------------------------------------------
>
> Key: BEAM-8199
> URL: https://issues.apache.org/jira/browse/BEAM-8199
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Valentyn Tymofieiev
> Priority: P2
> Labels: stale-P2
>
> Currently we have some performance benchmarks in Beam, however they are not always monitored and we may not notice when a regression happens, see [1].
> Filing this issue to improve the tooling. Note that if automation becomes too noisy (too many regressions) people likely won't be paying attention either.
> As a first step, we could monitor regression in 50th percentile of performance metrics we collect for benchmarks that we run repeatedly.
> cc: [~kamilwu] [~kasiak] [~markflyhigh]
> https://lists.apache.org/thread.html/51e000f16481451c207c00ac5e881aa4a46fa020922eddffd00ad527@%3Cdev.beam.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)