Try using mimalloc as the global allocator.

[tobz]

Work in progress.

[pr-commenter]

Regression Detector (Saluki)

Regression Detector Results

Run ID: a598053b-c2c6-4990-b3aa-18e277521905
Baseline: db8ea48
Comparison: 1b2102c

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

Significant changes in experiment optimization goals

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

perf	experiment	goal	Δ mean %	Δ mean % CI
❌	distribution_metrics	memory utilization	+77.31	[+77.12, +77.50]
❌	uds_dogstatsd_to_api_100mb_antagonistic	ingress throughput	-43.62	[-49.86, -37.39]
❌	uds_dogstatsd_to_api_1mb	ingress throughput	-96.69	[-96.72, -96.66]
❌	uds_dogstatsd_to_api_10mb	ingress throughput	-99.73	[-99.80, -99.66]
❌	uds_dogstatsd_to_api_100mb	ingress throughput	-99.97	[-99.97, -99.97]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
❌	distribution_metrics	memory utilization	+77.31	[+77.12, +77.50]
❌	uds_dogstatsd_to_api_100mb_antagonistic	ingress throughput	-43.62	[-49.86, -37.39]
❌	uds_dogstatsd_to_api_1mb	ingress throughput	-96.69	[-96.72, -96.66]
❌	uds_dogstatsd_to_api_10mb	ingress throughput	-99.73	[-99.80, -99.66]
❌	uds_dogstatsd_to_api_100mb	ingress throughput	-99.97	[-99.97, -99.97]

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]

Regression Detector (DogStatsD)

Regression Detector Results

Run ID: 3e81fb88-bd1b-4a59-b2c1-0944e21bb7fa
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
➖	distribution_metrics	memory utilization	+2.00	[+1.79, +2.21]
➖	uds_dogstatsd_to_api_100mb_antagonistic	ingress throughput	+0.01	[+0.00, +0.02]
➖	uds_dogstatsd_to_api_1mb	ingress throughput	+0.00	[-0.06, +0.06]
➖	uds_dogstatsd_to_api_100mb	ingress throughput	-0.01	[-0.02, +0.01]
➖	uds_dogstatsd_to_api_10mb	ingress throughput	-0.02	[-0.05, +0.01]

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

[tobz]

Going to close this for now as there wasn't enough evidence early on that we could reasonably overcome the large jumps in memory growth when switching to something other than the system allocator.

We may revisit this in the future.