-
Notifications
You must be signed in to change notification settings - Fork 3
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
flesh out an example multitenant strategy #243
base: multitenant-refactor-pt2
Are you sure you want to change the base?
flesh out an example multitenant strategy #243
Conversation
Signed-off-by: Luke Steensen <luke.steensen@gmail.com>
Regression Detector (Saluki)Regression Detector ResultsRun ID: 27b3b87e-e33a-4fa4-9399-f05d0c79b4ab Baseline: 1c64a0e Regression Detector: ❌ Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
❌ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +22.11 | [+21.95, +22.27] | 1 | |
➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.05 | [+0.00, +0.09] | 1 | |
➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | +0.01 | [-0.02, +0.04] | 1 | |
➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | +0.00 | [-0.00, +0.00] | 1 | |
➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.00 | [-0.03, +0.03] | 1 | |
➖ | dsd_uds_512kb_3k_contexts | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | |
➖ | dsd_uds_100mb_3k_contexts | ingress throughput | -0.01 | [-0.02, +0.01] | 1 | |
➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.01 | [-0.03, +0.01] | 1 | |
➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -1.18 | [-1.38, -0.97] | 1 | |
❌ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -18.75 | [-21.59, -15.92] | 1 | |
❌ | dsd_uds_500mb_3k_contexts | ingress throughput | -38.49 | [-38.57, -38.40] | 1 |
Explanation
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".
Regression Detector (DogStatsD)Regression Detector ResultsRun ID: 86772dd3-ff01-47a9-aad2-13f676c19890 Baseline: 7.55.2 Regression Detector: ✅ 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 |
---|---|---|---|---|---|---|
➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.04 | [+0.02, +0.07] | 1 | |
➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +0.01 | [-0.16, +0.17] | 1 | |
➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.01 | [-0.02, +0.04] | 1 | |
➖ | dsd_uds_1mb_50k_contexts | ingress throughput | +0.00 | [-0.00, +0.00] | 1 | |
➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.00 | [-0.04, +0.04] | 1 | |
➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | +0.00 | [-0.00, +0.00] | 1 | |
➖ | dsd_uds_500mb_3k_contexts | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | |
➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.01 | [-0.04, +0.02] | 1 | |
➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -0.01 | [-0.05, +0.02] | 1 |
Explanation
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".
Regression Detector LinksExperiment Result Links
|
Signed-off-by: Luke Steensen <luke.steensen@gmail.com>
This is not intended to be merged as-is, but serve as a starting point for something demo-able. There are currently a number of limitations that make it decidedly not production ready.