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

[CONTINT-4416] Optimize KSM configmap collection #32368

Conversation

ewoodthomas
Copy link
Contributor

@ewoodthomas ewoodthomas commented Dec 18, 2024

What does this PR do?

Optimizes collection of configmaps for the configmap.count metric. Previously the entire configmap was collected (including the data and binarydata) fields. This PR uses the meta.k8s.io API to exclusively collect metadata for configmaps and only store name, namespace, UID, and resourceVersion. These are the only fields necessary to generate the configmap.count metric.

Motivation

Collection of configmaps can be quite expensive in terms of cpu/memory/network. The DCA requested and stored the entire configmap. By only querying and storing metadata, we massively reduce the costs of collecting configmaps.

Describe how you validated your changes

  1. Deployed an agent with the changes
  2. Deployed an agent without the changes
  3. Deployed a massive amount of configmaps on both clusters using this script
#!/bin/bash

NUM_CONFIGMAPS=1000

DATA_SIZE_KB=100

NAMESPACE="configmap-test"

kubectl get namespace "$NAMESPACE" > /dev/null 2>&1 || kubectl create namespace "$NAMESPACE"

generate_large_data() {
  head -c "$((DATA_SIZE_KB * 1024))" /dev/urandom | base64 | tr -d '\n'
}

for i in $(seq 1 "$NUM_CONFIGMAPS"); do
  CONFIGMAP_NAME="large-configmap-$i"
  echo "Creating ConfigMap: $CONFIGMAP_NAME with ${DATA_SIZE_KB}KB of data"

  cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
metadata:
  name: $CONFIGMAP_NAME
  namespace: $NAMESPACE
data:
  payload: |
    $(generate_large_data)
EOF

done

echo "Finished creating $NUM_CONFIGMAPS ConfigMaps in namespace '$NAMESPACE'"

  1. Validated both metrics are identical
  2. Compared pod memory usage and validated that there is a spike with the old configmap collection and no spike with the new implementation

Old implementation with large spikes - Link to Data

Screenshot 2024-12-19 at 3 42 54 PM

New implementation with minimal spikes - Link to Data

Screenshot 2024-12-19 at 3 42 35 PM

Possible Drawbacks / Trade-offs

Additional Notes

@ewoodthomas ewoodthomas added the qa/done QA done before merge and regressions are covered by tests label Dec 18, 2024
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Dec 18, 2024
@ewoodthomas ewoodthomas changed the title Optimize kube_state configmap collection [CONTINT-4416] Optimize KSM configmap collection Dec 18, 2024
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Dec 18, 2024

Uncompressed package size comparison

Comparison with ancestor 3e0bdff730c0e24d15abd0dfc4068b1e37bbfb68

Diff per package
package diff status size ancestor threshold
datadog-agent-amd64-deb 0.01MB ⚠️ 1187.96MB 1187.96MB 140.00MB
datadog-agent-arm64-deb 0.01MB ⚠️ 933.96MB 933.95MB 140.00MB
datadog-agent-aarch64-rpm 0.01MB ⚠️ 943.20MB 943.19MB 140.00MB
datadog-agent-x86_64-rpm 0.01MB ⚠️ 1197.22MB 1197.22MB 140.00MB
datadog-agent-x86_64-suse 0.01MB ⚠️ 1197.22MB 1197.22MB 140.00MB
datadog-dogstatsd-amd64-deb 0.00MB 78.57MB 78.57MB 10.00MB
datadog-dogstatsd-x86_64-rpm 0.00MB 78.64MB 78.64MB 10.00MB
datadog-dogstatsd-x86_64-suse 0.00MB 78.64MB 78.64MB 10.00MB
datadog-dogstatsd-arm64-deb 0.00MB 55.77MB 55.77MB 10.00MB
datadog-heroku-agent-amd64-deb 0.00MB 504.87MB 504.87MB 70.00MB
datadog-iot-agent-amd64-deb 0.00MB 113.33MB 113.33MB 10.00MB
datadog-iot-agent-x86_64-rpm 0.00MB 113.40MB 113.40MB 10.00MB
datadog-iot-agent-x86_64-suse 0.00MB 113.40MB 113.40MB 10.00MB
datadog-iot-agent-arm64-deb 0.00MB 108.80MB 108.80MB 10.00MB
datadog-iot-agent-aarch64-rpm 0.00MB 108.87MB 108.87MB 10.00MB

Decision

⚠️ Warning

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Dec 18, 2024

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=51657549 --os-family=ubuntu

Note: This applies to commit 1bc0ea5

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Dec 18, 2024

[Fast Unit Tests Report]

On pipeline 51657549 (CI Visibility). The following jobs did not run any unit tests:

Jobs:
  • tests_flavor_dogstatsd_deb-x64
  • tests_flavor_heroku_deb-x64
  • tests_flavor_iot_deb-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

@ewoodthomas ewoodthomas marked this pull request as ready for review December 19, 2024 17:03
@ewoodthomas ewoodthomas requested review from a team as code owners December 19, 2024 17:03
@github-actions github-actions bot added medium review PR review might take time and removed short review PR is simple enough to be reviewed quickly labels Dec 19, 2024
Copy link

cit-pr-commenter bot commented Dec 19, 2024

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a87bb5c7-cdee-42c8-95b9-f75f4b1b13f4

Baseline: 3e0bdff
Comparison: 1bc0ea5
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +0.97 [-2.28, +4.22] 1 Logs
quality_gate_idle memory utilization +0.67 [+0.64, +0.70] 1 Logs bounds checks dashboard
otel_to_otel_logs ingress throughput +0.50 [-0.15, +1.15] 1 Logs
quality_gate_idle_all_features memory utilization +0.34 [+0.25, +0.43] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.07 [-0.39, +0.53] 1 Logs
file_to_blackhole_100ms_latency egress throughput +0.04 [-0.70, +0.79] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.04 [-0.87, +0.94] 1 Logs
file_to_blackhole_0ms_latency_http1 egress throughput +0.01 [-0.90, +0.92] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.01 [-0.10, +0.12] 1 Logs
file_to_blackhole_0ms_latency_http2 egress throughput +0.01 [-0.87, +0.89] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
file_to_blackhole_300ms_latency egress throughput -0.03 [-0.67, +0.61] 1 Logs
file_tree memory utilization -0.04 [-0.17, +0.09] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.04 [-0.11, +0.03] 1 Logs
file_to_blackhole_500ms_latency egress throughput -0.05 [-0.83, +0.73] 1 Logs
file_to_blackhole_1000ms_latency egress throughput -0.41 [-1.20, +0.39] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -2.97 [-3.64, -2.30] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
file_to_blackhole_0ms_latency lost_bytes 10/10
file_to_blackhole_0ms_latency memory_usage 10/10
file_to_blackhole_0ms_latency_http1 lost_bytes 10/10
file_to_blackhole_0ms_latency_http1 memory_usage 10/10
file_to_blackhole_0ms_latency_http2 lost_bytes 10/10
file_to_blackhole_0ms_latency_http2 memory_usage 10/10
file_to_blackhole_1000ms_latency memory_usage 10/10
file_to_blackhole_1000ms_latency_linear_load memory_usage 10/10
file_to_blackhole_100ms_latency lost_bytes 10/10
file_to_blackhole_100ms_latency memory_usage 10/10
file_to_blackhole_300ms_latency lost_bytes 10/10
file_to_blackhole_300ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency lost_bytes 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
quality_gate_idle memory_usage 10/10 bounds checks dashboard
quality_gate_idle_all_features memory_usage 10/10 bounds checks dashboard
quality_gate_logs lost_bytes 10/10
quality_gate_logs memory_usage 10/10

Explanation

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

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:

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

CI Pass/Fail Decision

Passed. All Quality Gates passed.

  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

Copy link
Member

@sblumenthal sblumenthal left a comment

Choose a reason for hiding this comment

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

Change looks good, small note on releasenotes file location

@ewoodthomas
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Dec 20, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-12-20 16:09:12 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 33m.


2024-12-20 16:48:25 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit fdd7787 into main Dec 20, 2024
219 checks passed
@dd-mergequeue dd-mergequeue bot deleted the ewoodthomas/CONTINT-4416_optimize_kubernetes_state_configmap_count_collection branch December 20, 2024 16:48
@github-actions github-actions bot added this to the 7.62.0 milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium review PR review might take time qa/done QA done before merge and regressions are covered by tests team/container-integrations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants