Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: use 3-sigma-rule in import time analysis #13073

Merged
merged 2 commits into from
Apr 7, 2025
Merged

Conversation

P403n1x87
Copy link
Contributor

@P403n1x87 P403n1x87 commented Apr 4, 2025

We increase the z-statistic threshold to 3 sigmas to reduce the potential reporting of false import time regressions.

Checklist

  • PR author has checked that all the criteria below are met
  • The PR description includes an overview of the change
  • The PR description articulates the motivation for the change
  • The change includes tests OR the PR description describes a testing strategy
  • The PR description notes risks associated with the change, if any
  • Newly-added code is easy to change
  • The change follows the library release note guidelines
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Reviewer has checked that all the criteria below are met
  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Newly-added code is easy to change
  • Release note makes sense to a user of the library
  • If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

We increase the z-statistic threshold to 3 sigmas to reduce the
potential reporting of false import time regressions.
@P403n1x87 P403n1x87 added the changelog/no-changelog A changelog entry is not required for this PR. label Apr 4, 2025
@P403n1x87 P403n1x87 requested a review from a team as a code owner April 4, 2025 14:58
@P403n1x87 P403n1x87 requested a review from erikayasuda April 4, 2025 14:58
@P403n1x87 P403n1x87 enabled auto-merge (squash) April 4, 2025 14:58
Copy link
Contributor

github-actions bot commented Apr 4, 2025

CODEOWNERS have been resolved as:

scripts/import-analysis/import_analysis.py                              @DataDog/apm-core-python

Copy link
Contributor

github-actions bot commented Apr 4, 2025

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 229 ± 2 ms.

The average import time from base is: 231 ± 2 ms.

The import time difference between this PR and base is: -2.12 ± 0.09 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.979 ms (0.86%)
ddtrace.bootstrap.sitecustomize 1.316 ms (0.57%)
ddtrace.bootstrap.preload 1.316 ms (0.57%)
ddtrace.internal.products 1.316 ms (0.57%)
ddtrace.internal.remoteconfig.client 0.641 ms (0.28%)
ddtrace 0.663 ms (0.29%)

@pr-commenter
Copy link

pr-commenter bot commented Apr 4, 2025

Benchmarks

Benchmark execution time: 2025-04-07 08:56:19

Comparing candidate commit f645e6d in PR branch ci/import-time-3sigma with baseline commit 93d1e12 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 490 metrics, 2 unstable metrics.

@P403n1x87 P403n1x87 merged commit cc77a7b into main Apr 7, 2025
332 checks passed
@P403n1x87 P403n1x87 deleted the ci/import-time-3sigma branch April 7, 2025 08:59
chojomok pushed a commit that referenced this pull request Apr 7, 2025
We increase the z-statistic threshold to 3 sigmas to reduce the
potential reporting of false import time regressions.

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [ ] Reviewer has checked that all the criteria below are met 
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants