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

Bump actions/download-artifact from 4.1.7 to 4.1.8 #27430

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 8, 2024

Bumps actions/download-artifact from 4.1.7 to 4.1.8.

Release notes

Sourced from actions/download-artifact's releases.

v4.1.8

What's Changed

Full Changelog: actions/download-artifact@v4...v4.1.8

Commits
  • fa0a91b Merge pull request #341 from actions/robherley/bump-pkgs
  • b54d088 Update @​actions/artifact version, bump dependencies
  • See full diff in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4.1.7 to 4.1.8.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@65a9edc...fa0a91b)

---
updated-dependencies:
- dependency-name: actions/download-artifact
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added changelog/no-changelog dependencies PRs that bump a dependency dev/tooling qa/no-code-change No code change in Agent code requiring validation team/agent-devx-infra labels Jul 8, 2024
@dependabot dependabot bot requested review from a team as code owners July 8, 2024 20:44
@dependabot dependabot bot added this to the Triage milestone Jul 8, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 8, 2024

The following labels could not be found: dependencies-github-actions.

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Jul 8, 2024

[Fast Unit Tests Report]

On pipeline 51073302 (CI Visibility). The following jobs did not run any unit tests:

Jobs:
  • tests_deb-arm64-py3
  • tests_deb-x64-py3
  • tests_flavor_dogstatsd_deb-x64
  • tests_flavor_heroku_deb-x64
  • tests_flavor_iot_deb-x64
  • tests_rpm-arm64-py3
  • tests_rpm-x64-py3
  • tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

@pr-commenter
Copy link

pr-commenter bot commented Jul 8, 2024

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 2139894e-8768-402c-be12-1784ee861eaf

Baseline: 777de39
Comparison: 64d94f2
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_idle_all_features memory utilization +1.11 [+0.99, +1.23] 1 Logs bounds checks dashboard
tcp_syslog_to_blackhole ingress throughput +0.57 [+0.52, +0.62] 1 Logs
quality_gate_idle memory utilization +0.21 [+0.17, +0.26] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.09 [-0.36, +0.55] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.04 [-0.78, +0.86] 1 Logs
file_to_blackhole_100ms_latency egress throughput +0.04 [-0.71, +0.78] 1 Logs
file_tree memory utilization +0.03 [-0.10, +0.15] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.01 [-0.75, +0.78] 1 Logs
file_to_blackhole_0ms_latency_http2 egress throughput +0.00 [-0.78, +0.79] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
uds_dogstatsd_to_api ingress throughput -0.00 [-0.10, +0.10] 1 Logs
file_to_blackhole_0ms_latency_http1 egress throughput -0.05 [-0.84, +0.75] 1 Logs
file_to_blackhole_300ms_latency egress throughput -0.05 [-0.68, +0.58] 1 Logs
file_to_blackhole_1000ms_latency egress throughput -0.06 [-0.85, +0.72] 1 Logs
otel_to_otel_logs ingress throughput -0.39 [-1.06, +0.28] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -1.11 [-1.85, -0.38] 1 Logs
quality_gate_logs % cpu utilization -1.74 [-4.64, +1.16] 1 Logs

Bounds Checks: ❌ Failed

perf experiment bounds_check_name replicates_passed links
file_to_blackhole_100ms_latency lost_bytes 9/10
file_to_blackhole_0ms_latency lost_bytes 10/10
file_to_blackhole_0ms_latency memory_usage 10/10
file_to_blackhole_0ms_latency_http1 lost_bytes 10/10
file_to_blackhole_0ms_latency_http1 memory_usage 10/10
file_to_blackhole_0ms_latency_http2 lost_bytes 10/10
file_to_blackhole_0ms_latency_http2 memory_usage 10/10
file_to_blackhole_1000ms_latency memory_usage 10/10
file_to_blackhole_1000ms_latency_linear_load memory_usage 10/10
file_to_blackhole_100ms_latency memory_usage 10/10
file_to_blackhole_300ms_latency lost_bytes 10/10
file_to_blackhole_300ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency lost_bytes 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
quality_gate_idle memory_usage 10/10 bounds checks dashboard
quality_gate_idle_all_features memory_usage 10/10 bounds checks dashboard
quality_gate_logs lost_bytes 10/10
quality_gate_logs memory_usage 10/10

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

Passed. All Quality Gates passed.

  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

@chouetz
Copy link
Member

chouetz commented Sep 23, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Sep 23, 2024

🚂 MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

@dd-devflow
Copy link

dd-devflow bot commented Sep 24, 2024

⚠️ MergeQueue: This merge request was unqueued

This merge request was unqueued

If you need support, contact us on Slack #devflow!

@chouetz chouetz requested a review from a team as a code owner December 11, 2024 13:40
@chouetz
Copy link
Member

chouetz commented Dec 11, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Dec 11, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-12-11 13:41:33 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-12-11 14:36:13 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 24m.


2024-12-11 14:36:42 UTCMergeQueue: This merge request has conflicts

This merge request conflicts with another merge request ahead in the queue.

The merge requests in front of this one are:

Please wait for the conflicting merge request(s) to merge. After they have merged, resolve any conflicts and add this merge request to the queue again.

@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Dec 11, 2024
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Dec 11, 2024

Package size comparison

Comparison with ancestor 777de397e7d5c10596b60bcbcbbec36be1c94d52

Diff per package
package diff status size ancestor threshold
datadog-agent-amd64-deb 0.00MB 1268.86MB 1268.86MB 140.00MB
datadog-iot-agent-amd64-deb 0.00MB 113.28MB 113.28MB 10.00MB
datadog-dogstatsd-amd64-deb 0.00MB 78.52MB 78.52MB 10.00MB
datadog-heroku-agent-amd64-deb 0.00MB 505.42MB 505.42MB 70.00MB
datadog-agent-x86_64-rpm 0.00MB 1278.09MB 1278.09MB 140.00MB
datadog-agent-x86_64-suse 0.00MB 1278.09MB 1278.09MB 140.00MB
datadog-iot-agent-x86_64-rpm 0.00MB 113.35MB 113.35MB 10.00MB
datadog-iot-agent-x86_64-suse 0.00MB 113.35MB 113.35MB 10.00MB
datadog-dogstatsd-x86_64-rpm 0.00MB 78.59MB 78.59MB 10.00MB
datadog-dogstatsd-x86_64-suse 0.00MB 78.59MB 78.59MB 10.00MB
datadog-agent-arm64-deb 0.00MB 1003.94MB 1003.94MB 140.00MB
datadog-iot-agent-arm64-deb 0.00MB 108.76MB 108.76MB 10.00MB
datadog-dogstatsd-arm64-deb 0.00MB 55.74MB 55.74MB 10.00MB
datadog-agent-aarch64-rpm 0.00MB 1013.15MB 1013.15MB 140.00MB
datadog-iot-agent-aarch64-rpm 0.00MB 108.83MB 108.83MB 10.00MB

Decision

✅ Passed

@chouetz
Copy link
Member

chouetz commented Dec 12, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Dec 12, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-12-12 10:24:48 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-12-12 14:24:51 UTC ⚠️ MergeQueue: This merge request was unqueued

This merge request was unqueued

@chouetz
Copy link
Member

chouetz commented Dec 12, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Dec 12, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-12-12 15:44:55 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-12-12 19:44:56 UTC ⚠️ MergeQueue: This merge request was unqueued

This merge request was unqueued

@chouetz
Copy link
Member

chouetz commented Dec 13, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Dec 13, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-12-13 13:48:49 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-12-13 14:55:45 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 30m.


2024-12-13 15:25:17 UTC ℹ️ MergeQueue: This merge request was merged

Copy link
Contributor

Serverless Benchmark Results

BenchmarkStartEndInvocation comparison between 777de39 and 3c97f2a.

tl;dr

Use these benchmarks as an insight tool during development.

  1. Skim down the vs base column in each chart. If there is a ~, then there was no statistically significant change to the benchmark. Otherwise, ensure the estimated percent change is either negative or very small.

  2. The last row of each chart is the geomean. Ensure this percentage is either negative or very small.

What is this benchmarking?

The BenchmarkStartEndInvocation compares the amount of time it takes to call the start-invocation and end-invocation endpoints. For universal instrumentation languages (Dotnet, Golang, Java, Ruby), this represents the majority of the duration overhead added by our tracing layer.

The benchmark is run using a large variety of lambda request payloads. In the charts below, there is one row for each event payload type.

How do I interpret these charts?

The charts below comes from benchstat. They represent the statistical change in duration (sec/op), memory overhead (B/op), and allocations (allocs/op).

The benchstat docs explain how to interpret these charts.

Before the comparison table, we see common file-level configuration. If there are benchmarks with different configuration (for example, from different packages), benchstat will print separate tables for each configuration.

The table then compares the two input files for each benchmark. It shows the median and 95% confidence interval summaries for each benchmark before and after the change, and an A/B comparison under "vs base". ... The p-value measures how likely it is that any differences were due to random chance (i.e., noise). The "~" means benchstat did not detect a statistically significant difference between the two inputs. ...

Note that "statistically significant" is not the same as "large": with enough low-noise data, even very small changes can be distinguished from noise and considered statistically significant. It is, of course, generally easier to distinguish large changes from noise.

Finally, the last row of the table shows the geometric mean of each column, giving an overall picture of how the benchmarks changed. Proportional changes in the geomean reflect proportional changes in the benchmarks. For example, given n benchmarks, if sec/op for one of them increases by a factor of 2, then the sec/op geomean will increase by a factor of ⁿ√2.

I need more help

First off, do not worry if the benchmarks are failing. They are not tests. The intention is for them to be a tool for you to use during development.

If you would like a hand interpreting the results come chat with us in #serverless-agent in the internal DataDog slack or in #serverless in the public DataDog slack. We're happy to help!

Benchmark stats
goos: linux
goarch: amd64
pkg: github.com/DataDog/datadog-agent/pkg/serverless/daemon
cpu: AMD EPYC 7763 64-Core Processor                
                                      │ baseline/benchmark.log │       current/benchmark.log        │
                                      │         sec/op         │   sec/op     vs base               │
api-gateway-appsec.json                            88.01µ ± 5%   86.60µ ± 1%  -1.61% (p=0.019 n=10)
api-gateway-kong-appsec.json                       67.87µ ± 1%   67.36µ ± 2%       ~ (p=0.631 n=10)
api-gateway-kong.json                              65.31µ ± 2%   64.60µ ± 1%       ~ (p=0.052 n=10)
api-gateway-non-proxy-async.json                   101.5µ ± 1%   103.6µ ± 2%  +2.01% (p=0.005 n=10)
api-gateway-non-proxy.json                         102.0µ ± 1%   101.8µ ± 1%       ~ (p=1.000 n=10)
api-gateway-websocket-connect.json                 68.87µ ± 4%   65.17µ ± 3%  -5.37% (p=0.001 n=10)
api-gateway-websocket-default.json                 60.01µ ± 3%   58.72µ ± 2%  -2.15% (p=0.015 n=10)
api-gateway-websocket-disconnect.json              59.30µ ± 2%   59.17µ ± 1%       ~ (p=0.481 n=10)
api-gateway.json                                   108.9µ ± 1%   108.4µ ± 1%  -0.45% (p=0.037 n=10)
application-load-balancer.json                     59.53µ ± 2%   58.76µ ± 1%  -1.30% (p=0.043 n=10)
cloudfront.json                                    45.26µ ± 3%   44.77µ ± 1%  -1.09% (p=0.043 n=10)
cloudwatch-events.json                             38.34µ ± 2%   38.18µ ± 1%       ~ (p=0.448 n=10)
cloudwatch-logs.json                               60.66µ ± 3%   60.65µ ± 1%       ~ (p=0.481 n=10)
custom.json                                        32.08µ ± 1%   32.13µ ± 1%       ~ (p=0.481 n=10)
dynamodb.json                                      85.38µ ± 1%   86.12µ ± 3%       ~ (p=0.190 n=10)
empty.json                                         30.88µ ± 2%   30.80µ ± 2%       ~ (p=0.971 n=10)
eventbridge-custom.json                            45.61µ ± 2%   46.97µ ± 1%  +2.98% (p=0.000 n=10)
eventbridge-no-bus.json                            44.99µ ± 1%   45.65µ ± 1%  +1.45% (p=0.000 n=10)
eventbridge-no-timestamp.json                      45.59µ ± 2%   46.01µ ± 1%       ~ (p=0.123 n=10)
eventbridgesns.json                                59.45µ ± 1%   59.68µ ± 1%       ~ (p=0.280 n=10)
eventbridgesqs.json                                64.78µ ± 1%   66.36µ ± 1%  +2.44% (p=0.000 n=10)
http-api.json                                      65.13µ ± 1%   66.36µ ± 1%  +1.88% (p=0.004 n=10)
kinesis-batch.json                                 65.29µ ± 1%   66.09µ ± 2%  +1.22% (p=0.029 n=10)
kinesis.json                                       52.01µ ± 0%   52.98µ ± 2%  +1.86% (p=0.029 n=10)
s3.json                                            55.62µ ± 2%   56.57µ ± 1%  +1.71% (p=0.002 n=10)
sns-batch.json                                     81.64µ ± 1%   84.10µ ± 1%  +3.02% (p=0.000 n=10)
sns.json                                           61.74µ ± 1%   63.53µ ± 1%  +2.90% (p=0.000 n=10)
snssqs.json                                        104.5µ ± 1%   106.4µ ± 0%  +1.88% (p=0.000 n=10)
snssqs_no_dd_context.json                          94.68µ ± 2%   96.85µ ± 1%  +2.29% (p=0.004 n=10)
sqs-aws-header.json                                53.31µ ± 1%   53.98µ ± 1%  +1.26% (p=0.003 n=10)
sqs-batch.json                                     85.70µ ± 1%   88.19µ ± 0%  +2.91% (p=0.002 n=10)
sqs.json                                           63.48µ ± 1%   65.26µ ± 1%  +2.80% (p=0.000 n=10)
sqs_no_dd_context.json                             58.45µ ± 0%   59.69µ ± 1%  +2.12% (p=0.000 n=10)
stepfunction.json                                  41.58µ ± 1%   42.37µ ± 1%  +1.91% (p=0.000 n=10)
geomean                                            62.03µ        62.46µ       +0.69%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │          B/op          │     B/op      vs base               │
api-gateway-appsec.json                           37.33Ki ± 0%   37.33Ki ± 0%       ~ (p=0.157 n=10)
api-gateway-kong-appsec.json                      26.90Ki ± 0%   26.90Ki ± 0%       ~ (p=0.349 n=10)
api-gateway-kong.json                             24.37Ki ± 0%   24.37Ki ± 0%       ~ (p=0.167 n=10)
api-gateway-non-proxy-async.json                  48.00Ki ± 0%   48.00Ki ± 0%       ~ (p=0.895 n=10)
api-gateway-non-proxy.json                        47.18Ki ± 0%   47.17Ki ± 0%       ~ (p=0.517 n=10)
api-gateway-websocket-connect.json                25.37Ki ± 0%   25.37Ki ± 0%       ~ (p=0.837 n=10)
api-gateway-websocket-default.json                21.26Ki ± 0%   21.26Ki ± 0%       ~ (p=0.537 n=10)
api-gateway-websocket-disconnect.json             21.02Ki ± 0%   21.02Ki ± 0%       ~ (p=0.565 n=10)
api-gateway.json                                  49.28Ki ± 0%   49.27Ki ± 0%       ~ (p=0.268 n=10)
application-load-balancer.json                    23.39Ki ± 0%   23.39Ki ± 0%       ~ (p=0.236 n=10)
cloudfront.json                                   17.45Ki ± 0%   17.45Ki ± 0%       ~ (p=0.108 n=10)
cloudwatch-events.json                            11.52Ki ± 0%   11.52Ki ± 0%       ~ (p=0.103 n=10)
cloudwatch-logs.json                              53.05Ki ± 0%   53.05Ki ± 0%       ~ (p=0.073 n=10)
custom.json                                       9.545Ki ± 0%   9.545Ki ± 0%       ~ (p=0.976 n=10)
dynamodb.json                                     40.33Ki ± 0%   40.33Ki ± 0%       ~ (p=0.303 n=10)
empty.json                                        9.083Ki ± 0%   9.083Ki ± 0%       ~ (p=0.742 n=10)
eventbridge-custom.json                           14.67Ki ± 0%   14.67Ki ± 0%       ~ (p=0.724 n=10)
eventbridge-no-bus.json                           13.63Ki ± 0%   13.63Ki ± 0%       ~ (p=0.598 n=10)
eventbridge-no-timestamp.json                     13.63Ki ± 0%   13.64Ki ± 0%  +0.01% (p=0.040 n=10)
eventbridgesns.json                               20.46Ki ± 0%   20.46Ki ± 0%       ~ (p=0.357 n=10)
eventbridgesqs.json                               24.59Ki ± 0%   24.60Ki ± 0%       ~ (p=0.533 n=10)
http-api.json                                     23.31Ki ± 0%   23.31Ki ± 0%       ~ (p=0.561 n=10)
kinesis-batch.json                                26.53Ki ± 0%   26.53Ki ± 0%       ~ (p=0.669 n=10)
kinesis.json                                      17.41Ki ± 0%   17.41Ki ± 0%       ~ (p=0.259 n=10)
s3.json                                           19.91Ki ± 0%   19.90Ki ± 0%       ~ (p=0.068 n=10)
sns-batch.json                                    39.07Ki ± 0%   39.08Ki ± 0%       ~ (p=0.420 n=10)
sns.json                                          24.49Ki ± 0%   24.49Ki ± 0%       ~ (p=0.925 n=10)
snssqs.json                                       52.74Ki ± 0%   52.74Ki ± 0%       ~ (p=0.880 n=10)
snssqs_no_dd_context.json                         46.50Ki ± 0%   46.50Ki ± 0%       ~ (p=0.693 n=10)
sqs-aws-header.json                               18.78Ki ± 0%   18.78Ki ± 0%       ~ (p=0.810 n=10)
sqs-batch.json                                    41.26Ki ± 0%   41.26Ki ± 0%       ~ (p=0.414 n=10)
sqs.json                                          25.39Ki ± 0%   25.39Ki ± 0%       ~ (p=0.643 n=10)
sqs_no_dd_context.json                            21.04Ki ± 0%   21.04Ki ± 0%       ~ (p=0.701 n=10)
stepfunction.json                                 13.54Ki ± 0%   13.54Ki ± 0%       ~ (p=0.876 n=10)
geomean                                           24.15Ki        24.15Ki       -0.00%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │       allocs/op        │ allocs/op   vs base                 │
api-gateway-appsec.json                             630.0 ± 0%   630.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-kong-appsec.json                        488.0 ± 0%   488.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-kong.json                               466.0 ± 0%   466.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-non-proxy-async.json                    723.0 ± 0%   723.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-non-proxy.json                          713.0 ± 0%   713.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-websocket-connect.json                  451.0 ± 0%   451.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-websocket-default.json                  376.0 ± 0%   376.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-websocket-disconnect.json               366.0 ± 0%   366.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway.json                                    785.0 ± 0%   785.0 ± 0%       ~ (p=1.000 n=10) ¹
application-load-balancer.json                      351.0 ± 0%   351.0 ± 0%       ~ (p=1.000 n=10) ¹
cloudfront.json                                     281.0 ± 0%   281.0 ± 0%       ~ (p=1.000 n=10) ¹
cloudwatch-events.json                              218.0 ± 0%   218.0 ± 0%       ~ (p=1.000 n=10) ¹
cloudwatch-logs.json                                211.0 ± 0%   211.0 ± 0%       ~ (p=1.000 n=10) ¹
custom.json                                         166.0 ± 0%   166.0 ± 0%       ~ (p=1.000 n=10) ¹
dynamodb.json                                       582.0 ± 0%   582.0 ± 0%       ~ (p=1.000 n=10) ¹
empty.json                                          157.0 ± 0%   157.0 ± 0%       ~ (p=1.000 n=10) ¹
eventbridge-custom.json                             261.0 ± 0%   261.0 ± 0%       ~ (p=1.000 n=10) ¹
eventbridge-no-bus.json                             252.0 ± 0%   252.0 ± 0%       ~ (p=1.000 n=10) ¹
eventbridge-no-timestamp.json                       252.0 ± 0%   252.0 ± 0%       ~ (p=1.000 n=10) ¹
eventbridgesns.json                                 318.0 ± 0%   318.0 ± 0%       ~ (p=1.000 n=10) ¹
eventbridgesqs.json                                 358.0 ± 0%   358.0 ± 0%       ~ (p=1.000 n=10) ¹
http-api.json                                       424.0 ± 0%   424.0 ± 0%       ~ (p=1.000 n=10) ¹
kinesis-batch.json                                  383.0 ± 0%   383.0 ± 0%       ~ (p=1.000 n=10) ¹
kinesis.json                                        279.0 ± 0%   279.0 ± 0%       ~ (p=1.000 n=10) ¹
s3.json                                             351.0 ± 0%   351.0 ± 0%       ~ (p=1.000 n=10) ¹
sns-batch.json                                      465.0 ± 0%   465.0 ± 0%       ~ (p=1.000 n=10) ¹
sns.json                                            336.0 ± 0%   336.0 ± 0%       ~ (p=1.000 n=10) ¹
snssqs.json                                         460.0 ± 0%   460.0 ± 0%       ~ (p=1.000 n=10) ¹
snssqs_no_dd_context.json                           420.0 ± 0%   420.0 ± 0%       ~ (p=1.000 n=10) ¹
sqs-aws-header.json                                 276.0 ± 0%   276.0 ± 0%       ~ (p=1.000 n=10) ¹
sqs-batch.json                                      500.0 ± 0%   500.0 ± 0%       ~ (p=1.000 n=10) ¹
sqs.json                                            351.0 ± 0%   351.0 ± 0%       ~ (p=1.000 n=10) ¹
sqs_no_dd_context.json                              337.0 ± 0%   337.0 ± 0%       ~ (p=1.000 n=10) ¹
stepfunction.json                                   226.0 ± 0%   226.0 ± 0%       ~ (p=1.000 n=10) ¹
geomean                                             360.1        360.1       +0.00%
¹ all samples are equal

@dd-mergequeue dd-mergequeue bot merged commit 28e9e7b into main Dec 13, 2024
216 of 217 checks passed
@dd-mergequeue dd-mergequeue bot deleted the dependabot/github_actions/actions/download-artifact-4.1.8 branch December 13, 2024 15:25
@github-actions github-actions bot modified the milestones: Triage, 7.62.0 Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog dependencies PRs that bump a dependency dev/tooling qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-devx-infra
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants