upgrade(installer): Enable static build of the installer #29478
Conversation
Go Package Import DifferencesBaseline: 42c6d41
|
BaptisteFoy
force-pushed
the
baptiste.foy/FA/static-installer
branch
from
3172adf
to
2479462
Compare
BaptisteFoy
force-pushed
the
baptiste.foy/FA/static-installer
branch
from
2479462
to
62e0308
Compare
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=44848401 --os-family=ubuntuNote: This applies to commit 7ae8343 |
Regression DetectorRegression Detector ResultsRun ID: 706bbd39-70ac-44c8-aec1-cd6a9ba26e45 Metrics dashboard Target profiles Baseline: 42c6d41 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | pycheck_lots_of_tags | % cpu utilization | +1.31 | [-1.17, +3.79] | 1 | Logs |
| ➖ | otel_to_otel_logs | ingress throughput | +0.77 | [-0.05, +1.58] | 1 | Logs |
| ➖ | idle | memory utilization | +0.33 | [+0.28, +0.38] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.05 | [-0.06, +0.16] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.10, +0.08] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.39 | [-1.12, +0.35] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.46 | [-0.51, -0.41] | 1 | Logs |
| ➖ | basic_py_check | % cpu utilization | -1.32 | [-3.98, +1.35] | 1 | Logs |
Bounds Checks
| perf | experiment | bounds_check_name | replicates_passed |
|---|---|---|---|
| ✅ | idle | 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:
-
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".
BaptisteFoy
added
changelog/no-changelog
qa/done
|
📥 📢 Info, this pull request increases the binary size of serverless extension by 72608 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 0ms. Debug infoIf 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 Benchmark Results
tl;drUse these benchmarks as an insight tool during development.
What is this benchmarking?The 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 The benchstat docs explain how to interpret these charts.
I need more helpFirst 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 Benchmark stats |
What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes