-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[AGENTRUN-466] Strip cluster-agent binaries #37813
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
Conversation
Gitlab CI Configuration Changes
|
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 9 | 0 | 0 |
ℹ️ Diff available in the job log.
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 67df56f Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +2.35 | [-0.44, +5.15] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.44 | [+0.39, +0.49] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.35 | [+0.19, +0.51] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.25 | [+0.13, +0.37] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.13 | [+0.06, +0.20] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.11 | [-0.44, +0.66] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.05 | [-0.56, +0.65] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.00 | [-0.61, +0.62] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.27, +0.27] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.01] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.02 | [-0.64, +0.60] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.05 | [-0.58, +0.48] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.06 | [-0.62, +0.50] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.08 | [-0.32, +0.16] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.08 | [-0.65, +0.49] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.16 | [-0.31, -0.02] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.19 | [-0.32, -0.07] | 1 | Logs |
➖ | file_tree | memory utilization | -0.31 | [-0.45, -0.17] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.32 | [-3.24, +2.60] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.43 | [-1.30, +0.43] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.45 | [-0.54, -0.36] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | -0.64 | [-0.72, -0.55] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.75 | [-0.81, -0.68] | 1 | Logs bounds checks dashboard |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 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 intake_connections: 10/10 replicas passed. Gate 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_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
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The figures are so significant that I’m wondering if we could have had the same result with -ldflags="-s -w"
?
I just checked the output of a build job and it seems we only have -ldflags="… -w"
-ldflags="-s"
is for:
-s disable symbol table
So, I’m wondering if it would have the same effect as strip
?
👋 Hey @L3n41c sorry I didn't see the comment before the PR got merged ! I believe strip is pretty much equivalent to using |
What does this PR do?
Strip cluster-agent binaries.
Motivation
Reduce cluster-agent binary size by 45MiB and docker image size by 30MiB.
Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes
I discussed this with container-platform and they considered it was probably just forgotten.
Other binaries in other images are stripped.
The unstripped binary is needed for fips compliance checks, so I had to keep an unstripped version in the artifacts.