Skip to content
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

fix(tag_cardinality_limit transform): mitigate performance bottleneck #19281

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

dsmith3197
Copy link
Contributor

@dsmith3197 dsmith3197 commented Dec 1, 2023

This avoids calling BloomFilter::count which has a time complexity of O(n) where n is the number of bits in the filter.

@dsmith3197 dsmith3197 requested a review from a team December 1, 2023 17:23
@github-actions github-actions bot added the domain: transforms Anything related to Vector's transform components label Dec 1, 2023
Copy link

github-actions bot commented Dec 1, 2023

Your preview site for the VRL Playground will be ready in a few minutes, please allow time for it to build.

Heres your preview link:
VRL Playground preview

@dsmith3197
Copy link
Contributor Author

/ci-run-regression

@@ -29,8 +63,7 @@ impl AcceptedTagValueSet {
let storage = match &mode {
Mode::Exact => TagValueSetStorage::Set(HashSet::with_capacity(value_limit)),
Mode::Probabilistic(config) => {
let num_bits = config.cache_size_per_key / 8; // Convert bytes to bits
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This conversion was wrong and BloomFilter::with_size takes the size in bytes, not bits, as an argument.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doh.

Copy link

github-actions bot commented Dec 1, 2023

Regression Detector Results

Run ID: c95e23d0-49e2-4044-b555-06f889b77ec5
Baseline: ce615d0
Comparison: 62a5328
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8112.44 [+8104.85, +8120.02] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8112.44 [+8104.85, +8120.02] 100.00%
file_to_blackhole egress throughput +0.97 [-1.59, +3.53] 46.72%
http_to_http_acks ingress throughput -0.18 [-1.48, +1.12] 18.16%
fluent_elasticsearch ingress throughput -0.32 [-0.79, +0.16] 72.46%
splunk_hec_route_s3 ingress throughput -1.46 [-1.98, -0.93] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8112.44 [+8104.85, +8120.02] 100.00%
syslog_log2metric_humio_metrics ingress throughput +1.98 [+1.84, +2.12] 100.00%
syslog_splunk_hec_logs ingress throughput +1.78 [+1.73, +1.84] 100.00%
socket_to_socket_blackhole ingress throughput +1.52 [+1.44, +1.60] 100.00%
file_to_blackhole egress throughput +0.97 [-1.59, +3.53] 46.72%
otlp_http_to_blackhole ingress throughput +0.78 [+0.62, +0.93] 100.00%
otlp_grpc_to_blackhole ingress throughput +0.77 [+0.68, +0.86] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput +0.74 [+0.63, +0.84] 100.00%
syslog_humio_logs ingress throughput +0.72 [+0.64, +0.80] 100.00%
syslog_log2metric_splunk_hec_metrics ingress throughput +0.54 [+0.40, +0.68] 100.00%
syslog_loki ingress throughput +0.46 [+0.40, +0.52] 100.00%
http_text_to_http_json ingress throughput +0.45 [+0.31, +0.60] 100.00%
http_to_s3 ingress throughput +0.23 [-0.05, +0.50] 82.52%
http_to_http_noack ingress throughput +0.16 [+0.06, +0.26] 98.97%
http_elasticsearch ingress throughput +0.03 [-0.05, +0.10] 40.21%
http_to_http_json ingress throughput +0.02 [-0.05, +0.10] 42.60%
datadog_agent_remap_blackhole_acks ingress throughput +0.01 [-0.09, +0.12] 16.36%
splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.13, +0.14] 2.51%
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.13, +0.14] 2.34%
syslog_regex_logs2metric_ddmetrics ingress throughput -0.02 [-0.14, +0.09] 23.98%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.03 [-0.14, +0.09] 29.05%
enterprise_http_to_http ingress throughput -0.07 [-0.14, +0.00] 88.50%
datadog_agent_remap_datadog_logs ingress throughput -0.13 [-0.23, -0.04] 97.52%
http_to_http_acks ingress throughput -0.18 [-1.48, +1.12] 18.16%
fluent_elasticsearch ingress throughput -0.32 [-0.79, +0.16] 72.46%
datadog_agent_remap_blackhole ingress throughput -0.72 [-0.84, -0.59] 100.00%
splunk_hec_route_s3 ingress throughput -1.46 [-1.98, -0.93] 100.00%

@dsmith3197 dsmith3197 requested review from a team as code owners December 1, 2023 18:15
@github-actions github-actions bot added the domain: external docs Anything related to Vector's external, public documentation label Dec 1, 2023
Copy link
Member

@jszwedko jszwedko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice find!

@@ -29,8 +63,7 @@ impl AcceptedTagValueSet {
let storage = match &mode {
Mode::Exact => TagValueSetStorage::Set(HashSet::with_capacity(value_limit)),
Mode::Probabilistic(config) => {
let num_bits = config.cache_size_per_key / 8; // Convert bytes to bits
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doh.

Comment on lines +22 to +23
/// Count of items inserted into the bloom filter.
/// We manually track this because `BloomFilter::count` has O(n) time complexity.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 to this comment

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also represents a different value. The bloom filter, if it is counting the bits in the filter, can only return the number of reduced items, which will frequently (usually?) be less than the number of actual items inserted in the filter.

@@ -59,3 +92,47 @@ impl AcceptedTagValueSet {
};
}
}

#[cfg(test)]
mod tests {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 to these tests.

Copy link
Member

@jszwedko jszwedko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm remembering this separately maintained count used to exist but then I dropped it in #17911 since I thought it was maintained separately only because the old bloom filter type didn't have a way to fetch the count.

@dsmith3197 dsmith3197 enabled auto-merge December 1, 2023 18:35
@@ -86,7 +86,7 @@ const fn default_value_limit() -> usize {
}

pub(crate) const fn default_cache_size() -> usize {
5000 * 1024 // 5KB
5 * 1024 // 5KB
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a potential behavior change, in that it will cause more false positives for sites that have not explictly configured the cache size.

Comment on lines +22 to +23
/// Count of items inserted into the bloom filter.
/// We manually track this because `BloomFilter::count` has O(n) time complexity.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also represents a different value. The bloom filter, if it is counting the bits in the filter, can only return the number of reduced items, which will frequently (usually?) be less than the number of actual items inserted in the filter.

@datadog-vectordotdev
Copy link

Datadog Report

Branch report: dougsmith/tag-cardinality-limit
Commit report: dc427d8

vector: 0 Failed, 0 New Flaky, 2019 Passed, 0 Skipped, 1m 22.85s Wall Time

@dsmith3197 dsmith3197 added this pull request to the merge queue Dec 1, 2023
Copy link

github-actions bot commented Dec 1, 2023

Regression Detector Results

Run ID: 248f4a82-ca98-49e0-9ed4-c72d63176611
Baseline: 1cc16f8
Comparison: 23d828a
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8094.64 [+8086.99, +8102.29] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8094.64 [+8086.99, +8102.29] 100.00%
http_to_http_acks ingress throughput -0.36 [-1.67, +0.94] 35.11%
splunk_hec_route_s3 ingress throughput -1.25 [-1.77, -0.73] 99.99%
file_to_blackhole egress throughput -1.99 [-4.43, +0.45] 82.09%
fluent_elasticsearch ingress throughput -3.02 [-3.49, -2.55] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8094.64 [+8086.99, +8102.29] 100.00%
otlp_http_to_blackhole ingress throughput +3.04 [+2.88, +3.19] 100.00%
syslog_regex_logs2metric_ddmetrics ingress throughput +2.84 [+2.72, +2.97] 100.00%
http_elasticsearch ingress throughput +1.80 [+1.73, +1.88] 100.00%
socket_to_socket_blackhole ingress throughput +1.57 [+1.48, +1.66] 100.00%
syslog_splunk_hec_logs ingress throughput +0.64 [+0.58, +0.71] 100.00%
syslog_humio_logs ingress throughput +0.56 [+0.47, +0.66] 100.00%
http_to_http_noack ingress throughput +0.21 [+0.11, +0.31] 99.96%
http_text_to_http_json ingress throughput +0.09 [-0.04, +0.22] 75.38%
http_to_http_json ingress throughput +0.06 [-0.02, +0.13] 77.34%
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.01 [-0.13, +0.14] 4.79%
splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.13, +0.14] 2.52%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.03 [-0.14, +0.08] 36.27%
http_to_s3 ingress throughput -0.05 [-0.32, +0.22] 24.22%
enterprise_http_to_http ingress throughput -0.07 [-0.16, +0.02] 77.55%
syslog_loki ingress throughput -0.15 [-0.25, -0.06] 99.14%
http_to_http_acks ingress throughput -0.36 [-1.67, +0.94] 35.11%
otlp_grpc_to_blackhole ingress throughput -0.43 [-0.52, -0.34] 100.00%
datadog_agent_remap_datadog_logs ingress throughput -0.59 [-0.68, -0.49] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput -0.64 [-0.72, -0.56] 100.00%
syslog_log2metric_splunk_hec_metrics ingress throughput -0.82 [-0.97, -0.68] 100.00%
splunk_hec_route_s3 ingress throughput -1.25 [-1.77, -0.73] 99.99%
datadog_agent_remap_blackhole ingress throughput -1.28 [-1.39, -1.17] 100.00%
datadog_agent_remap_blackhole_acks ingress throughput -1.32 [-1.43, -1.21] 100.00%
file_to_blackhole egress throughput -1.99 [-4.43, +0.45] 82.09%
fluent_elasticsearch ingress throughput -3.02 [-3.49, -2.55] 100.00%
syslog_log2metric_humio_metrics ingress throughput -3.66 [-3.79, -3.53] 100.00%

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 1, 2023
Copy link

github-actions bot commented Dec 1, 2023

Regression Detector Results

Run ID: f687d12f-ea75-4dc8-b89c-1c92d7b5cfac
Baseline: 79e4bdf
Comparison: 6e9096e
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8083.48 [+8075.59, +8091.36] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8083.48 [+8075.59, +8091.36] 100.00%
file_to_blackhole egress throughput +2.14 [-0.33, +4.62] 84.58%
http_to_http_acks ingress throughput -0.31 [-1.61, +0.99] 30.37%
splunk_hec_route_s3 ingress throughput -0.43 [-0.93, +0.08] 83.28%
fluent_elasticsearch ingress throughput -3.18 [-3.65, -2.70] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8083.48 [+8075.59, +8091.36] 100.00%
otlp_http_to_blackhole ingress throughput +3.32 [+3.16, +3.48] 100.00%
syslog_log2metric_humio_metrics ingress throughput +2.62 [+2.48, +2.75] 100.00%
socket_to_socket_blackhole ingress throughput +2.45 [+2.38, +2.51] 100.00%
file_to_blackhole egress throughput +2.14 [-0.33, +4.62] 84.58%
http_elasticsearch ingress throughput +1.78 [+1.71, +1.85] 100.00%
otlp_grpc_to_blackhole ingress throughput +1.24 [+1.15, +1.33] 100.00%
syslog_log2metric_splunk_hec_metrics ingress throughput +0.65 [+0.51, +0.79] 100.00%
syslog_loki ingress throughput +0.41 [+0.35, +0.47] 100.00%
syslog_splunk_hec_logs ingress throughput +0.32 [+0.26, +0.39] 100.00%
http_text_to_http_json ingress throughput +0.28 [+0.16, +0.40] 99.99%
http_to_s3 ingress throughput +0.11 [-0.17, +0.38] 47.21%
syslog_regex_logs2metric_ddmetrics ingress throughput +0.06 [-0.05, +0.18] 61.88%
http_to_http_json ingress throughput +0.06 [-0.02, +0.13] 76.57%
http_to_http_noack ingress throughput +0.05 [-0.03, +0.13] 71.28%
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.14, +0.14] 0.37%
splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.14, +0.14] 1.40%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.05 [-0.17, +0.06] 54.89%
enterprise_http_to_http ingress throughput -0.08 [-0.18, +0.01] 85.12%
syslog_humio_logs ingress throughput -0.12 [-0.21, -0.03] 96.79%
http_to_http_acks ingress throughput -0.31 [-1.61, +0.99] 30.37%
splunk_hec_route_s3 ingress throughput -0.43 [-0.93, +0.08] 83.28%
datadog_agent_remap_blackhole_acks ingress throughput -0.57 [-0.66, -0.48] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput -0.99 [-1.08, -0.89] 100.00%
datadog_agent_remap_datadog_logs ingress throughput -1.55 [-1.64, -1.46] 100.00%
datadog_agent_remap_blackhole ingress throughput -1.87 [-1.97, -1.76] 100.00%
fluent_elasticsearch ingress throughput -3.18 [-3.65, -2.70] 100.00%

@jszwedko jszwedko added this pull request to the merge queue Dec 1, 2023
@neuronull neuronull removed this pull request from the merge queue due to a manual request Dec 2, 2023
Copy link

github-actions bot commented Dec 2, 2023

Regression Detector Results

Run ID: 9df2330e-d484-49f2-8f6f-ac8c16fabb60
Baseline: 5aef4bd
Comparison: c4ecb0a
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8096.65 [+8088.19, +8105.11] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8096.65 [+8088.19, +8105.11] 100.00%
splunk_hec_route_s3 ingress throughput +1.96 [+1.44, +2.48] 100.00%
file_to_blackhole egress throughput +0.95 [-1.58, +3.49] 46.51%
http_to_http_acks ingress throughput +0.50 [-0.81, +1.81] 47.06%
fluent_elasticsearch ingress throughput -2.60 [-3.07, -2.13] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8096.65 [+8088.19, +8105.11] 100.00%
otlp_http_to_blackhole ingress throughput +2.95 [+2.80, +3.10] 100.00%
splunk_hec_route_s3 ingress throughput +1.96 [+1.44, +2.48] 100.00%
socket_to_socket_blackhole ingress throughput +1.83 [+1.75, +1.92] 100.00%
datadog_agent_remap_datadog_logs ingress throughput +1.40 [+1.30, +1.50] 100.00%
otlp_grpc_to_blackhole ingress throughput +1.09 [+0.99, +1.18] 100.00%
http_elasticsearch ingress throughput +0.96 [+0.89, +1.03] 100.00%
file_to_blackhole egress throughput +0.95 [-1.58, +3.49] 46.51%
http_text_to_http_json ingress throughput +0.85 [+0.72, +0.98] 100.00%
http_to_http_acks ingress throughput +0.50 [-0.81, +1.81] 47.06%
datadog_agent_remap_blackhole_acks ingress throughput +0.42 [+0.32, +0.53] 100.00%
http_to_http_noack ingress throughput +0.14 [+0.05, +0.23] 99.24%
http_to_http_json ingress throughput +0.01 [-0.06, +0.08] 15.46%
splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.13, +0.14] 2.48%
splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.14, +0.14] 1.64%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.03 [-0.15, +0.08] 38.27%
enterprise_http_to_http ingress throughput -0.12 [-0.19, -0.04] 98.40%
http_to_s3 ingress throughput -0.15 [-0.43, +0.12] 64.33%
datadog_agent_remap_blackhole ingress throughput -0.68 [-0.78, -0.59] 100.00%
syslog_humio_logs ingress throughput -0.69 [-0.80, -0.58] 100.00%
syslog_splunk_hec_logs ingress throughput -0.73 [-0.79, -0.67] 100.00%
syslog_log2metric_splunk_hec_metrics ingress throughput -0.88 [-1.02, -0.73] 100.00%
syslog_log2metric_humio_metrics ingress throughput -1.19 [-1.32, -1.07] 100.00%
syslog_loki ingress throughput -1.33 [-1.39, -1.28] 100.00%
syslog_regex_logs2metric_ddmetrics ingress throughput -1.46 [-1.59, -1.32] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput -1.81 [-1.89, -1.72] 100.00%
fluent_elasticsearch ingress throughput -2.60 [-3.07, -2.13] 100.00%

@jszwedko jszwedko added this pull request to the merge queue Dec 2, 2023
Copy link

github-actions bot commented Dec 2, 2023

Regression Detector Results

Run ID: a9ace7b3-f1b2-47e9-bd95-462ace0cff85
Baseline: ab54db1
Comparison: 5f39bee
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8097.13 [+8089.04, +8105.21] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8097.13 [+8089.04, +8105.21] 100.00%
file_to_blackhole egress throughput +0.76 [-1.64, +3.16] 39.93%
splunk_hec_route_s3 ingress throughput +0.14 [-0.38, +0.67] 34.57%
http_to_http_acks ingress throughput -0.01 [-1.32, +1.30] 1.04%
fluent_elasticsearch ingress throughput -2.80 [-3.27, -2.33] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +8097.13 [+8089.04, +8105.21] 100.00%
socket_to_socket_blackhole ingress throughput +2.80 [+2.72, +2.88] 100.00%
otlp_http_to_blackhole ingress throughput +2.13 [+1.99, +2.28] 100.00%
syslog_humio_logs ingress throughput +1.92 [+1.82, +2.03] 100.00%
otlp_grpc_to_blackhole ingress throughput +1.15 [+1.06, +1.24] 100.00%
http_elasticsearch ingress throughput +0.97 [+0.89, +1.04] 100.00%
file_to_blackhole egress throughput +0.76 [-1.64, +3.16] 39.93%
splunk_hec_route_s3 ingress throughput +0.14 [-0.38, +0.67] 34.57%
http_to_http_noack ingress throughput +0.12 [+0.03, +0.22] 97.17%
http_to_http_json ingress throughput +0.01 [-0.06, +0.08] 15.23%
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.13, +0.14] 3.89%
splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.13, +0.14] 2.50%
http_to_http_acks ingress throughput -0.01 [-1.32, +1.30] 1.04%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.03 [-0.14, +0.09] 28.75%
http_to_s3 ingress throughput -0.06 [-0.34, +0.21] 29.09%
enterprise_http_to_http ingress throughput -0.10 [-0.16, -0.04] 99.56%
datadog_agent_remap_datadog_logs ingress throughput -0.18 [-0.27, -0.08] 99.76%
syslog_log2metric_splunk_hec_metrics ingress throughput -0.22 [-0.37, -0.08] 98.76%
syslog_loki ingress throughput -0.39 [-0.46, -0.32] 100.00%
syslog_log2metric_humio_metrics ingress throughput -0.54 [-0.67, -0.41] 100.00%
syslog_splunk_hec_logs ingress throughput -0.55 [-0.63, -0.48] 100.00%
datadog_agent_remap_blackhole_acks ingress throughput -0.62 [-0.72, -0.51] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput -0.82 [-0.91, -0.74] 100.00%
http_text_to_http_json ingress throughput -1.88 [-2.00, -1.75] 100.00%
syslog_regex_logs2metric_ddmetrics ingress throughput -2.60 [-2.73, -2.47] 100.00%
fluent_elasticsearch ingress throughput -2.80 [-3.27, -2.33] 100.00%
datadog_agent_remap_blackhole ingress throughput -3.10 [-3.25, -2.96] 100.00%

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 2, 2023
@pront pront added this pull request to the merge queue Dec 4, 2023
Copy link

github-actions bot commented Dec 4, 2023

Regression Detector Results

Run ID: e618fae7-14d2-4e5f-abba-28ff37c68c13
Baseline: 8abe8e5
Comparison: b3b50b3
Total CPUs: 7

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

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +7988.95 [+7981.00, +7996.90] 100.00%

Experiments that were not declared erratic but were detected as being so, coefficient of variation cutoff 0.10:

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +7988.95 [+7981.00, +7996.90] 100.00%
fluent_elasticsearch ingress throughput +0.96 [+0.49, +1.44] 99.91%
file_to_blackhole egress throughput -1.60 [-4.01, +0.81] 72.39%
http_to_http_acks ingress throughput -2.13 [-3.43, -0.84] 99.32%
splunk_hec_route_s3 ingress throughput -2.88 [-3.40, -2.36] 100.00%

Fine details of change detection per experiment.

experiment goal Δ mean % Δ mean % CI confidence
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +7988.95 [+7981.00, +7996.90] 100.00%
syslog_log2metric_humio_metrics ingress throughput +4.64 [+4.50, +4.78] 100.00%
syslog_regex_logs2metric_ddmetrics ingress throughput +2.44 [+2.33, +2.54] 100.00%
http_text_to_http_json ingress throughput +2.09 [+1.96, +2.23] 100.00%
otlp_http_to_blackhole ingress throughput +1.73 [+1.58, +1.88] 100.00%
socket_to_socket_blackhole ingress throughput +1.57 [+1.51, +1.62] 100.00%
fluent_elasticsearch ingress throughput +0.96 [+0.49, +1.44] 99.91%
datadog_agent_remap_datadog_logs ingress throughput +0.66 [+0.56, +0.75] 100.00%
otlp_grpc_to_blackhole ingress throughput +0.42 [+0.33, +0.52] 100.00%
http_elasticsearch ingress throughput +0.41 [+0.35, +0.48] 100.00%
http_to_http_noack ingress throughput +0.17 [+0.09, +0.24] 99.96%
http_to_s3 ingress throughput +0.04 [-0.24, +0.31] 17.96%
http_to_http_json ingress throughput +0.01 [-0.06, +0.08] 20.29%
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.14, +0.14] 0.39%
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.14, +0.14] 1.00%
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.05 [-0.17, +0.06] 55.66%
enterprise_http_to_http ingress throughput -0.13 [-0.20, -0.06] 99.84%
datadog_agent_remap_blackhole_acks ingress throughput -0.46 [-0.57, -0.35] 100.00%
datadog_agent_remap_datadog_logs_acks ingress throughput -0.61 [-0.68, -0.53] 100.00%
syslog_humio_logs ingress throughput -0.93 [-1.03, -0.83] 100.00%
syslog_log2metric_splunk_hec_metrics ingress throughput -0.98 [-1.12, -0.83] 100.00%
syslog_splunk_hec_logs ingress throughput -1.43 [-1.51, -1.36] 100.00%
datadog_agent_remap_blackhole ingress throughput -1.57 [-1.66, -1.48] 100.00%
file_to_blackhole egress throughput -1.60 [-4.01, +0.81] 72.39%
syslog_loki ingress throughput -1.84 [-1.90, -1.77] 100.00%
http_to_http_acks ingress throughput -2.13 [-3.43, -0.84] 99.32%
splunk_hec_route_s3 ingress throughput -2.88 [-3.40, -2.36] 100.00%

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 4, 2023
@jszwedko
Copy link
Member

jszwedko commented Dec 4, 2023

This is blocked from merging due to a bug in the regression detector that is flagging positive changes as blocking. I'll merge manually.

This avoids calling BloomFilter::count which has a time complexity of O(n) where n is the number of bits in the filter.
@jszwedko jszwedko force-pushed the dougsmith/tag-cardinality-limit branch from 127ab11 to 42683ef Compare December 4, 2023 15:02
@jszwedko jszwedko merged commit 42683ef into master Dec 4, 2023
24 of 25 checks passed
@jszwedko jszwedko deleted the dougsmith/tag-cardinality-limit branch December 4, 2023 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: external docs Anything related to Vector's external, public documentation domain: transforms Anything related to Vector's transform components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants