DataDog / saluki

An experimental toolkit for building telemetry data planes in Rust.
Apache License 2.0
12 stars 2 forks source link

[APR-208] fix: handle duplicate tags when hashing context #209

Closed tobz closed 3 weeks ago

tobz commented 3 weeks ago

Context

In #161, we mention that we currently don't handle duplicate tags in metrics, which is to say we don't do anything special to avoid or cope with them. This is mostly relevant to context hashing, as our use of XOR hashing for tags (in order to be oblivious to the order of the tags themselves) presents an issue when duplicate tags are present, as it would potentially cancel out a previous tags hash, leaving us with a subpar context hash overall.

Solution

This PR adds proper handling of duplicate tags by ignoring them while hashing a context. We introduce a simple bit of "have we seen this before?" logic, tracking seen hashes for each operation using a reusable HashSet<T> stored on ContextResolver.

This has necessitated some slight reorganization of how we create ContextRef<'a, I> but is otherwise slightly cleaner and line count equivalent with the prior approach.

pr-commenter[bot] commented 3 weeks ago

Regression Detector (DogStatsD)

Regression Detector Results

Run ID: 7bd161a1-36c1-464b-a2aa-d7593a9f0c57

Baseline: 7.52.0 Comparison: 7.52.1

Performance changes are noted in the perf column of each table:

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_10mb_3k_contexts | ingress throughput | +0.05 | [+0.01, +0.09] | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +0.00 | [+0.00, +0.01] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | +0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -0.00 | [-0.07, +0.07] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | -0.00 | [-0.02, +0.01] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.02 | [-0.03, +0.00] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.02 | [-0.08, +0.05] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.02 | [-0.08, +0.04] | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | -2.33 | [-2.54, -2.12] | |

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] commented 3 weeks ago

Regression Detector (Saluki)

Regression Detector Results

Run ID: f9a8c089-6a23-4bcf-b3ab-8d2b436971ec

Baseline: 55e6b624b853261d7a0e8047d52e27e6c07e458f Comparison: 3d8977d7ea81e2a32394f59d2ac3d00b152871d2

Performance changes are noted in the perf column of each table:

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 | +3.71 | [+3.54, +3.87] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.06 | [-0.21, +0.34] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.02 | [-0.12, +0.17] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | -0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.00 | [-0.07, +0.07] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | -0.00 | [-0.01, +0.01] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | -0.01 | [-0.05, +0.03] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.02 | [-0.07, +0.03] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | -0.04 | [-0.09, +0.01] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -1.24 | [-4.55, +2.06] | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | -3.33 | [-3.42, -3.24] | |

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] commented 3 weeks ago

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]