Shift left performance #15
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stalep
reviewed
Jan 10, 2023
stalep
reviewed
Jan 10, 2023
stalep
reviewed
Jan 10, 2023
stalep
reviewed
Jan 10, 2023
stalep
reviewed
Jan 10, 2023
johnaohara
force-pushed
the
shift-left-perf
branch
from
6e46cc7 to
9eace40
Compare
|
@stalep please can you review this PR again? The easiest way to view the rendered post is here: https://github.com/johnaohara/redhatperf.github.io/blob/shift-left-perf/content/post/shift-left-on-performance/index.adoc |
stalep
reviewed
Mar 10, 2025
|
|
||
| == Problem Statement | ||
|
|
||
| How can performance engineering teams enable Eng / QE / SRE to integrate Performance Testing into their workflows, to reduce the risk that performance regressions propagate through to production services? |
There was a problem hiding this comment.
Should we add "product releases" in addition to production services?
|
|
||
| source: https://insights.sei.cmu.edu/blog/four-types-of-shift-left-testing/ | ||
|
|
||
| Not only do we want to include performance tests earlier in the dev/release cycle, we also want to ensure that the full suite of performance tests (or any proxy performance tests footnoteL[Citation needed]) captures performance regressions before multiple release cycles have occurred. |
|
|
||
| Receive report & analysis of impact of changes to key performance metrics | ||
|
|
||
| Allow automated capture of profiling data of system under load, allowing engineers to *see* what thier changes are doing under realistic scenarios |
|
|
||
| == Integration with Analytical Tools | ||
|
|
||
| In order to understand the performance characteristic of a service running in production, the all of the performance metrics captured at different stages of testing (dev, CI/CD, production) need to be accessible for a performance engineer to analyse. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.