Open gabedos opened 6 hours ago
Baseline: 924a1502fdb70f35064838fa1bbf27b54459fb1b Comparison: 65c7000c92c294d18b17e7dd1711728e3bc8b2a2
binary | os | arch | change |
---|---|---|---|
agent | linux | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
agent | linux | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
agent | windows | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
agent | darwin | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
agent | darwin | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
cluster-agent | linux | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
cluster-agent | linux | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
dogstatsd | linux | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
dogstatsd | linux | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
process-agent | linux | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
process-agent | linux | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
process-agent | windows | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
process-agent | darwin | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
process-agent | darwin | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
security-agent | linux | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
security-agent | linux | arm64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
security-agent | windows | amd64 | +1, -0
+github.com/DataDog/datadog-agent/pkg/util/gpu
|
Metrics dashboard
Target profiles
Run ID: 4451cfef-588a-4cca-829e-119eb15af5f9
Baseline: 924a1502fdb70f35064838fa1bbf27b54459fb1b Comparison: 65c7000c92c294d18b17e7dd1711728e3bc8b2a2 Diff
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_idle | memory_usage | 9/10 | bounds checks dashboard |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | 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_all_features | memory_usage | 10/10 | bounds checks dashboard |
❌ Failed. Some Quality Gates were violated.
What does this PR do?
Motivation
Describe how to test/QA your changes
Deploy basic agent configuration with cluster tagger
Deploy a dummy GPU workload
k apply -f deployment.yaml
Check for the GPU tags on the cluster agent
Possible Drawbacks / Trade-offs
Additional Notes
Considered creating 1 ParsePods method shared across kubeapiserver and kubelet collectors however the overhead work to convert the types or implement interfaces seem like more work than supporting the two separate parsers.