[AGNTLOG-222] - adjust serverless to always utilize gzip compression#37523
Conversation
|
/merge |
|
View all feedbacks in Devflow UI.
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.
The expected merge time in
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 8ad866f Optimization Goals: ❌ Regression(s) detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ❌ | quality_gate_logs | % cpu utilization | +7.76 | [+4.88, +10.65] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +2.20 | [+1.35, +3.04] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +0.57 | [+0.44, +0.71] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.37 | [+0.31, +0.43] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.10 | [+0.01, +0.19] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.08 | [-0.48, +0.64] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.05 | [-0.01, +0.10] | 1 | Logs |
| ➖ | file_to_blackhole_300ms_latency | egress throughput | +0.02 | [-0.64, +0.67] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.01 | [-0.62, +0.63] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.00 | [-0.61, +0.62] | 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.28, +0.28] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.01 | [-0.24, +0.22] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.02 | [-0.63, +0.59] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.04 | [-0.67, +0.60] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.09 | [-0.21, +0.02] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.11 | [-0.27, +0.05] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.11 | [-0.70, +0.48] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.19 | [-0.36, -0.02] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | -0.19 | [-0.27, -0.11] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.33 | [-0.45, -0.21] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -0.69 | [-3.75, +2.36] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -1.82 | [-1.91, -1.74] | 1 | Logs |
Bounds Checks: ❌ Failed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ❌ | docker_containers_memory | memory_usage | 0/10 | |
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | |
| ✅ | docker_containers_memory | simple_check_run | 10/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 | lost_bytes | 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 | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
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_idle_all_features, bounds check intake_connections: 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_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
### What does this PR do? Use `zstd` compression. We just need to enable add the `zstd` build tag (in DataDog/datadog-lambda-extension#878) [Before this change](https://github.com/DataDog/serverless-init-performance-testing/blob/main/saved-profiles/cpu-glib.pb.gz): <img width="1000" height="62" alt="Screenshot 2025-09-29 at 12 45 16 PM" src="https://github.com/user-attachments/assets/306a6233-db57-4617-8d3e-c65adcd73537" /> [After this change](https://github.com/DataDog/serverless-init-performance-testing/blob/main/saved-profiles/cpu-zstd.pb.gz): <img width="1000" height="62" alt="Screenshot 2025-09-29 at 12 45 24 PM" src="https://github.com/user-attachments/assets/402ffddd-e8b1-45e8-8bce-9fddddf5b5e3" /> The cum% for `(*batchStrategy).addMessage` goes down from 20.16% to 4.12%. <img width="500" height="425" alt="Screenshot 2025-09-29 at 5 13 42 PM" src="https://github.com/user-attachments/assets/a95ac5ed-577b-4ed1-81dd-fd97e17a9782" /> For more information, see [this one-pager](https://docs.google.com/document/d/1ovNSaNk_rZKcF3SDz8Ol5ypCD_MRqpq25MsnxMgTmPU/edit?usp=sharing). This PR pretty much just reverts #37523 ### Motivation Improving serverless-init performance https://datadoghq.atlassian.net/browse/SVLS-7667 ### Describe how you validated your changes - Unit tests - Manual testing & [profiling the agent](https://github.com/DataDog/serverless-init-performance-testing) - [Serverless self-monitoring tests](https://gitlab.ddbuild.io/DataDog/serverless-init-self-monitoring/-/pipelines/77863262). It has monitors to make sure we are still receiving logs/metrics/traces - [Serverless e2e tests](https://gitlab.ddbuild.io/DataDog/serverless-e2e-serverless-init-gcp-tests/-/pipelines/77869595/). Failures are known issues and unrelated to this change. ### Additional Notes
What does this PR do?
Revert to gzip compression for serverless log-agent endpoints
Motivation
Describe how you validated your changes
Automated testing is expected to cover the entirety of the verification requirements.
Possible Drawbacks / Trade-offs
Additional Notes