ci: don't fail with perf regressions on releases

[brettlangdon]

This is a stop gap to unblock releases which introduce known performance regressions. In the future we need to continue to block releases that introduce a performance regression. This PR is meant as a quick fix since we don't have any other ways to signal to the release process that we accept the regression.

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

[github-actions]

CODEOWNERS have been resolved as:

.gitlab/benchmarks/microbenchmarks.yml                                  @DataDog/python-guild @DataDog/apm-core-python

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 232 ± 3 ms.

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

The import time difference between this PR and base is: -1.1 ± 0.1 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.916 ms (0.83%)

ddtrace.bootstrap.sitecustomize 1.255 ms (0.54%)

ddtrace.bootstrap.preload 1.255 ms (0.54%)

ddtrace.internal.products 1.255 ms (0.54%)

ddtrace.internal.remoteconfig.client 0.615 ms (0.27%)

ddtrace 0.662 ms (0.29%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-04-09 15:43:30

Comparing candidate commit ac89396 in PR branch brettlangdon/release.check.perf with baseline commit fe66a15 in branch main.

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

[github-actions]

The backport to 2.21 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.21 2.21
# Navigate to the new working tree
cd .worktrees/backport-2.21
# Create a new branch
git switch --create backport-13135-to-2.21
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 698db4a943ffc7d7aec33c2a9a0cff389fce5249
# Push it to GitHub
git push --set-upstream origin backport-13135-to-2.21
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.21

Then, create a pull request where the base branch is 2.21 and the compare/head branch is backport-13135-to-2.21.