[USMON-779] usm: kafka: Changed kafka_last_tcp_seq_per_connection map size

[guyarb]

What does this PR do?

Instead of being matched to MaxTrackedConnections (which can reach up to 130K, we use MaxUSMConcurrentRequests which is set to 30k)

Motivation

Reduce the size of the map from 15MB to 3.5MB in staging environment.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: ecbeea84-5756-483e-9277-f9b4cbe1555e Baseline: 4dc2f37f5a7e54f59e356eda7ef218cf39198263 Comparison: 72f5da29bd91d555f9f20bde797533cb89cacbad Total CPUs: 7

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

Experiments with missing or malformed data

• basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	-0.40	[-6.94, +6.15]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	otel_to_otel_logs	ingress throughput	+1.18	[+0.56, +1.81]
➖	file_tree	memory utilization	+0.13	[+0.04, +0.22]
➖	tcp_syslog_to_blackhole	ingress throughput	+0.01	[-0.04, +0.07]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.00, +0.00]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]
➖	trace_agent_msgpack	ingress throughput	-0.01	[-0.01, -0.00]
➖	process_agent_standard_check_with_stats	memory utilization	-0.01	[-0.04, +0.02]
➖	trace_agent_json	ingress throughput	-0.01	[-0.05, +0.02]
➖	process_agent_real_time_mode	memory utilization	-0.03	[-0.07, +0.00]
➖	idle	memory utilization	-0.16	[-0.20, -0.13]
➖	process_agent_standard_check	memory utilization	-0.24	[-0.28, -0.20]
➖	file_to_blackhole	% cpu utilization	-0.40	[-6.94, +6.15]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.63	[-3.04, -0.22]

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

[guyarb]

Covered by #23124