[APR-240] Add support for configuring the idle connection timeout for HTTP clients.

[rayz]

Context

When building an HTTP client, we should be able to configure the maximum idle connection age before the connection is terminated. Open connections consume resources on the downstream target systems, and we should prefer to be sparing with how long we try to hold on to reusable resources before we declare the efficiency gains we stand to make not worth the imposition on the downstream target systems themselves.

Solution

Use Builder::pool_idle_timeout

Value hard coded to 45s in datadog-agent

[pr-commenter[bot]]

Regression Detector (DogStatsD)

Regression Detector Results

Run ID: cccdb753-4ff2-4c08-a663-7f8d0aed6320

Baseline: 7.52.0 Comparison: 7.52.1

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 | links | |------|----------------------------------------------|--------------------|----------|----------------|-------| | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +0.86 | [+0.66, +1.07] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | +0.03 | [+0.00, +0.06] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | +0.02 | [-0.05, +0.08] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.00 | [-0.02, +0.03] | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | -0.00 | [-0.01, +0.00] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | -0.01 | [-0.04, +0.03] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | -0.01 | [-0.02, +0.00] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.03 | [-0.09, +0.02] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.03 | [-0.07, +0.00] | |

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]]

Regression Detector (Saluki)

Regression Detector Results

Run ID: 891cc666-7204-4aec-beec-2c5d9f79e928

Baseline: d28654ab78d9eff74f88ac8ea4c8f8f6da3928c5 Comparison: d680bce4052341cb2e27051410337b7a9526c2d2

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 | links | |------|-------------------------------------------------|--------------------|----------|----------------|-------| | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +0.17 | [+0.07, +0.26] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.05 | [-0.04, +0.13] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.01 | [-0.26, +0.28] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | +0.01 | [-0.15, +0.17] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | +0.00 | [-0.05, +0.06] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.00 | [-0.01, +0.02] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | -0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.02 | [-0.03, -0.00] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.03 | [-0.14, +0.07] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -0.34 | [-3.55, +2.86] | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | -0.73 | [-0.86, -0.61] | |

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]]

Regression Detector Links

Experiment Result Links

experiment	link(s)
dsd_uds_100mb_250k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_100mb_3k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_100mb_3k_contexts_distributions_only	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_10mb_3k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_3k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_50k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_50k_contexts_memlimit	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_500mb_3k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_512kb_3k_contexts	[Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_50mb_10k_contexts_no_inlining (ADP only)	[Profiling (ADP)] [SMP Dashboard]
dsd_uds_50mb_10k_contexts_no_inlining_no_allocs (ADP only)	[Profiling (ADP)] [SMP Dashboard]