datadog-agent icon indicating copy to clipboard operation
datadog-agent copied to clipboard

trace: allow http2 plaintext on trace server

Open wdauchy opened this issue 1 year ago • 19 comments

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

wdauchy avatar Sep 05 '24 16:09 wdauchy

Go Package Import Differences

Baseline: b61cc33b2a1bde21a9f0e68b2a2e049d7c2b9b30 Comparison: 64ad8aee3d15fdced79043ff46e4f5d3e612b35d

binaryosarchchange
serverlesslinuxamd64
+1, -0
+golang.org/x/net/http2/h2c
serverlesslinuxarm64
+1, -0
+golang.org/x/net/http2/h2c

cit-pr-commenter[bot] avatar Sep 05 '24 16:09 cit-pr-commenter[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 07:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 07:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 07:09 github-actions[bot]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=48061036 --os-family=ubuntu

Note: This applies to commit 64ad8aee

pr-commenter[bot] avatar Sep 06 '24 08:09 pr-commenter[bot]

Regression Detector

Regression Detector Results

Run ID: 2df0813d-61ee-4949-8b8d-28c8a00a5491 Metrics dashboard Target profiles

Baseline: b61cc33b2a1bde21a9f0e68b2a2e049d7c2b9b30 Comparison: 64ad8aee3d15fdced79043ff46e4f5d3e612b35d

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
pycheck_lots_of_tags % cpu utilization +1.71 [-0.78, +4.19] 1 Logs
basic_py_check % cpu utilization +0.97 [-1.72, +3.66] 1 Logs
file_tree memory utilization +0.62 [+0.50, +0.75] 1 Logs
idle_all_features memory utilization +0.42 [+0.32, +0.52] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency egress throughput +0.20 [-0.29, +0.68] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.04 [-0.20, +0.29] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.02 [-0.32, +0.36] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.01, +0.01] 1 Logs
file_to_blackhole_300ms_latency egress throughput -0.00 [-0.19, +0.18] 1 Logs
file_to_blackhole_100ms_latency egress throughput -0.01 [-0.23, +0.22] 1 Logs
uds_dogstatsd_to_api ingress throughput -0.02 [-0.13, +0.08] 1 Logs
quality_gate_idle memory utilization -0.17 [-0.22, -0.12] 1 Logs bounds checks dashboard
tcp_syslog_to_blackhole ingress throughput -0.39 [-0.44, -0.34] 1 Logs
idle memory utilization -0.43 [-0.47, -0.38] 1 Logs bounds checks dashboard
quality_gate_idle_all_features memory utilization -0.56 [-0.66, -0.46] 1 Logs bounds checks dashboard
otel_to_otel_logs ingress throughput -0.73 [-1.53, +0.08] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -0.84 [-1.57, -0.11] 1 Logs

Bounds Checks

perf experiment bounds_check_name replicates_passed
file_to_blackhole_0ms_latency memory_usage 10/10
file_to_blackhole_1000ms_latency memory_usage 10/10
file_to_blackhole_100ms_latency memory_usage 10/10
file_to_blackhole_300ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
idle memory_usage 10/10
idle_all_features memory_usage 10/10
quality_gate_idle memory_usage 10/10
quality_gate_idle_all_features memory_usage 10/10

Explanation

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".

pr-commenter[bot] avatar Sep 06 '24 08:09 pr-commenter[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 09:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 09:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 09:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 09:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 10:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 12:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 12:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 12:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210592 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 06 '24 17:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 206496 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 10 '24 15:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 206496 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Sep 10 '24 15:09 github-actions[bot]

:warning::rotating_light: Warning, this pull request increases the binary size of serverless extension by 210560 bytes. Each MB of binary size increase means about 10ms of additional cold start time, so this pull request would increase cold start time by 2ms.

Debug info

If you have questions, we are happy to help, come visit us in the #serverless slack channel and provide a link to this comment.

These dependencies were added to the serverless extension by this pull request:

golang.org/x/net/http2

View dependency graphs for each added dependency in the artifacts section of the github action.

We suggest you consider adding the !serverless build tag to remove any new dependencies not needed in the serverless extension.

github-actions[bot] avatar Nov 01 '24 17:11 github-actions[bot]

Serverless Benchmark Results

BenchmarkStartEndInvocation comparison between b61cc33b2a1bde21a9f0e68b2a2e049d7c2b9b30 and 8f32af7060cf5038fbaa36dadf92e66eba9bdacc.

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                            89.45µ ± 4%   89.90µ ± 13%       ~ (p=1.000 n=10)
api-gateway-kong-appsec.json                       71.98µ ± 2%   69.44µ ±  2%  -3.53% (p=0.000 n=10)
api-gateway-kong.json                              69.80µ ± 1%   69.36µ ±  4%       ~ (p=0.280 n=10)
api-gateway-non-proxy-async.json                   109.9µ ± 1%   109.3µ ±  2%       ~ (p=0.529 n=10)
api-gateway-non-proxy.json                         108.8µ ± 1%   107.6µ ±  2%       ~ (p=0.190 n=10)
api-gateway-websocket-connect.json                 72.79µ ± 2%   71.88µ ±  3%       ~ (p=0.481 n=10)
api-gateway-websocket-default.json                 65.20µ ± 1%   62.89µ ±  1%  -3.54% (p=0.000 n=10)
api-gateway-websocket-disconnect.json              65.48µ ± 2%   63.17µ ±  1%  -3.53% (p=0.000 n=10)
api-gateway.json                                   119.1µ ± 2%   115.3µ ±  3%  -3.19% (p=0.001 n=10)
application-load-balancer.json                     65.41µ ± 1%   64.34µ ±  2%       ~ (p=0.052 n=10)
cloudfront.json                                    49.08µ ± 3%   48.30µ ±  7%       ~ (p=0.739 n=10)
cloudwatch-events.json                             40.13µ ± 3%   38.59µ ±  1%  -3.83% (p=0.000 n=10)
cloudwatch-logs.json                               68.80µ ± 2%   66.11µ ±  2%  -3.91% (p=0.000 n=10)
custom.json                                        32.97µ ± 1%   32.13µ ±  3%  -2.53% (p=0.002 n=10)
dynamodb.json                                      97.76µ ± 3%   93.83µ ±  3%  -4.02% (p=0.000 n=10)
empty.json                                         31.47µ ± 2%   30.29µ ±  4%  -3.73% (p=0.009 n=10)
eventbridge-custom.json                            50.64µ ± 2%   47.62µ ±  3%  -5.98% (p=0.000 n=10)
eventbridge-no-bus.json                            48.73µ ± 1%   46.73µ ±  1%  -4.10% (p=0.000 n=10)
eventbridge-no-timestamp.json                      48.39µ ± 2%   47.19µ ±  1%  -2.50% (p=0.002 n=10)
eventbridgesns.json                                67.11µ ± 1%   64.66µ ±  2%  -3.64% (p=0.000 n=10)
eventbridgesqs.json                                73.11µ ± 4%   72.83µ ±  1%       ~ (p=0.579 n=10)
http-api.json                                      74.92µ ± 1%   73.92µ ±  2%  -1.33% (p=0.029 n=10)
kinesis-batch.json                                 72.52µ ± 1%   74.26µ ±  2%  +2.40% (p=0.000 n=10)
kinesis.json                                       55.61µ ± 2%   56.57µ ±  1%  +1.73% (p=0.011 n=10)
s3.json                                            60.86µ ± 3%   61.37µ ±  2%       ~ (p=0.481 n=10)
sns-batch.json                                     95.12µ ± 3%   93.90µ ±  1%  -1.29% (p=0.004 n=10)
sns.json                                           69.85µ ± 2%   69.11µ ±  3%       ~ (p=0.853 n=10)
snssqs.json                                        122.4µ ± 1%   122.6µ ±  2%       ~ (p=0.579 n=10)
snssqs_no_dd_context.json                          109.6µ ± 2%   108.8µ ±  2%       ~ (p=0.436 n=10)
sqs-aws-header.json                                60.70µ ± 2%   61.51µ ±  3%       ~ (p=0.247 n=10)
sqs-batch.json                                     99.26µ ± 2%   97.05µ ±  3%  -2.23% (p=0.043 n=10)
sqs.json                                           74.26µ ± 3%   73.28µ ±  2%       ~ (p=0.123 n=10)
sqs_no_dd_context.json                             68.90µ ± 2%   69.96µ ±  2%  +1.53% (p=0.035 n=10)
stepfunction.json                                  48.04µ ± 5%   47.40µ ±  3%       ~ (p=0.481 n=10)
geomean                                            68.46µ        67.32µ        -1.66%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │          B/op          │     B/op      vs base               │
api-gateway-appsec.json                           37.34Ki ± 0%   37.34Ki ± 0%       ~ (p=0.985 n=10)
api-gateway-kong-appsec.json                      26.94Ki ± 0%   26.93Ki ± 0%       ~ (p=0.567 n=10)
api-gateway-kong.json                             24.44Ki ± 0%   24.43Ki ± 0%       ~ (p=0.540 n=10)
api-gateway-non-proxy-async.json                  48.14Ki ± 0%   48.14Ki ± 0%       ~ (p=0.839 n=10)
api-gateway-non-proxy.json                        47.36Ki ± 0%   47.35Ki ± 0%       ~ (p=0.699 n=10)
api-gateway-websocket-connect.json                25.53Ki ± 0%   25.53Ki ± 0%       ~ (p=0.897 n=10)
api-gateway-websocket-default.json                21.44Ki ± 0%   21.44Ki ± 0%       ~ (p=0.403 n=10)
api-gateway-websocket-disconnect.json             21.22Ki ± 0%   21.22Ki ± 0%       ~ (p=0.424 n=10)
api-gateway.json                                  49.60Ki ± 0%   49.60Ki ± 0%       ~ (p=0.643 n=10)
application-load-balancer.json                    23.31Ki ± 0%   23.31Ki ± 0%       ~ (p=0.617 n=10)
cloudfront.json                                   17.68Ki ± 0%   17.68Ki ± 0%       ~ (p=1.000 n=10)
cloudwatch-events.json                            11.74Ki ± 0%   11.74Ki ± 0%       ~ (p=0.725 n=10)
cloudwatch-logs.json                              53.38Ki ± 0%   53.38Ki ± 0%       ~ (p=0.171 n=10)
custom.json                                       9.751Ki ± 0%   9.750Ki ± 0%       ~ (p=0.752 n=10)
dynamodb.json                                     40.84Ki ± 0%   40.81Ki ± 0%  -0.08% (p=0.016 n=10)
empty.json                                        9.314Ki ± 0%   9.311Ki ± 0%       ~ (p=0.726 n=10)
eventbridge-custom.json                           15.04Ki ± 0%   15.01Ki ± 0%       ~ (p=0.159 n=10)
eventbridge-no-bus.json                           14.01Ki ± 0%   14.00Ki ± 0%       ~ (p=0.644 n=10)
eventbridge-no-timestamp.json                     13.99Ki ± 0%   14.02Ki ± 0%  +0.21% (p=0.019 n=10)
eventbridgesns.json                               20.96Ki ± 0%   20.96Ki ± 0%       ~ (p=0.986 n=10)
eventbridgesqs.json                               25.19Ki ± 0%   25.19Ki ± 0%       ~ (p=0.403 n=10)
http-api.json                                     23.98Ki ± 0%   23.96Ki ± 0%       ~ (p=0.271 n=10)
kinesis-batch.json                                27.09Ki ± 0%   27.16Ki ± 0%  +0.28% (p=0.009 n=10)
kinesis.json                                      17.94Ki ± 0%   17.95Ki ± 1%       ~ (p=0.985 n=10)
s3.json                                           20.46Ki ± 1%   20.45Ki ± 1%       ~ (p=0.565 n=10)
sns-batch.json                                    39.95Ki ± 0%   39.91Ki ± 0%       ~ (p=0.725 n=10)
sns.json                                          25.19Ki ± 0%   25.17Ki ± 1%       ~ (p=0.698 n=10)
snssqs.json                                       53.96Ki ± 0%   53.91Ki ± 0%       ~ (p=0.143 n=10)
snssqs_no_dd_context.json                         47.65Ki ± 0%   47.56Ki ± 1%  -0.19% (p=0.025 n=10)
sqs-aws-header.json                               19.49Ki ± 0%   19.47Ki ± 1%       ~ (p=0.184 n=10)
sqs-batch.json                                    42.30Ki ± 1%   42.32Ki ± 0%       ~ (p=0.315 n=10)
sqs.json                                          26.19Ki ± 1%   26.09Ki ± 1%  -0.40% (p=0.043 n=10)
sqs_no_dd_context.json                            21.88Ki ± 1%   21.98Ki ± 1%       ~ (p=0.225 n=10)
stepfunction.json                                 14.27Ki ± 1%   14.23Ki ± 1%       ~ (p=0.592 n=10)
geomean                                           24.62Ki        24.61Ki       -0.03%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │       allocs/op        │ allocs/op   vs base                 │
api-gateway-appsec.json                             629.5 ± 0%   629.5 ± 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                    726.0 ± 0%   725.5 ± 0%       ~ (p=0.650 n=10)
api-gateway-non-proxy.json                          716.0 ± 0%   716.0 ± 0%       ~ (p=1.000 n=10)
api-gateway-websocket-connect.json                  453.0 ± 0%   453.0 ± 0%       ~ (p=1.000 n=10)
api-gateway-websocket-default.json                  379.0 ± 0%   379.0 ± 0%       ~ (p=1.000 n=10)
api-gateway-websocket-disconnect.json               370.0 ± 0%   370.0 ± 0%       ~ (p=0.474 n=10)
api-gateway.json                                    791.0 ± 0%   791.0 ± 0%       ~ (p=0.087 n=10)
application-load-balancer.json                      353.0 ± 0%   353.0 ± 0%       ~ (p=1.000 n=10) ¹
cloudfront.json                                     284.0 ± 0%   284.0 ± 0%       ~ (p=1.000 n=10)
cloudwatch-events.json                              220.0 ± 0%   220.0 ± 0%       ~ (p=0.474 n=10)
cloudwatch-logs.json                                216.0 ± 0%   215.0 ± 0%       ~ (p=0.170 n=10)
custom.json                                         168.0 ± 0%   168.0 ± 1%       ~ (p=1.000 n=10)
dynamodb.json                                       589.0 ± 0%   589.0 ± 0%       ~ (p=0.365 n=10)
empty.json                                          160.0 ± 1%   160.0 ± 1%       ~ (p=1.000 n=10)
eventbridge-custom.json                             266.5 ± 0%   266.0 ± 0%       ~ (p=0.141 n=10)
eventbridge-no-bus.json                             258.0 ± 0%   257.5 ± 0%       ~ (p=0.650 n=10)
eventbridge-no-timestamp.json                       257.0 ± 0%   258.0 ± 0%  +0.39% (p=0.020 n=10)
eventbridgesns.json                                 326.0 ± 0%   326.0 ± 0%       ~ (p=0.785 n=10)
eventbridgesqs.json                                 367.0 ± 0%   367.0 ± 0%       ~ (p=0.704 n=10)
http-api.json                                       435.0 ± 0%   434.5 ± 0%       ~ (p=0.741 n=10)
kinesis-batch.json                                  391.0 ± 0%   392.0 ± 0%  +0.26% (p=0.010 n=10)
kinesis.json                                        286.5 ± 0%   287.0 ± 1%       ~ (p=0.932 n=10)
s3.json                                             359.0 ± 1%   359.0 ± 1%       ~ (p=0.996 n=10)
sns-batch.json                                      479.0 ± 0%   478.0 ± 0%       ~ (p=0.672 n=10)
sns.json                                            347.0 ± 0%   347.0 ± 1%       ~ (p=0.918 n=10)
snssqs.json                                         479.0 ± 0%   479.0 ± 0%       ~ (p=0.120 n=10)
snssqs_no_dd_context.json                           437.0 ± 1%   436.0 ± 1%  -0.23% (p=0.030 n=10)
sqs-aws-header.json                                 287.0 ± 0%   287.0 ± 1%       ~ (p=0.546 n=10)
sqs-batch.json                                      516.0 ± 1%   517.0 ± 0%       ~ (p=0.216 n=10)
sqs.json                                            364.0 ± 1%   362.0 ± 2%       ~ (p=0.053 n=10)
sqs_no_dd_context.json                              349.5 ± 1%   351.0 ± 1%       ~ (p=0.238 n=10)
stepfunction.json                                   237.0 ± 1%   237.0 ± 1%       ~ (p=0.663 n=10)
geomean                                             367.3        367.2       -0.02%
¹ all samples are equal

github-actions[bot] avatar Nov 01 '24 17:11 github-actions[bot]