Parallelize benchmarks

[brettlangdon]

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
.gitlab/download-wheels-from-gh-actions.sh                              @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 ± 2 ms.

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

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

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.962 ms (0.85%)

ddtrace.bootstrap.sitecustomize 1.288 ms (0.56%)

ddtrace.bootstrap.preload 1.288 ms (0.56%)

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

ddtrace 0.674 ms (0.29%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-05-14 19:47:32

Comparing candidate commit 2ba36b2 in PR branch brettlangdon/benchmark.parallel with baseline commit ca14026 in branch main.

Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥
Check Gitlab CI job log to find if any benchmark has crashed.

Scenarios present only in candidate:

• iast_aspects-upper_noaspect

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

scenario:iast_aspects-format_aspect

• 🟥 execution_time [+275.843ns; +324.537ns] or [+7.886%; +9.278%]

scenario:iast_aspects-strip_aspect

• 🟥 execution_time [+1.497µs; +1.591µs] or [+11.584%; +12.313%]