Performance Regression or Improvement: sideinpts_python_batch_1gb_1kb_10workers_1000window_1key_percent_dict:runtime

[github-actions]

Performance change found in the
test: sideinpts_python_batch_1gb_1kb_10workers_1000window_1key_percent_dict for the metric: runtime.

For more information on how to triage the alerts, please look at
Triage performance alert issues section of the README.

Test description: python | Side Input | 1 GB dictionary, 1% of keys, 1000 fixed windows
Test Link -

beam/.test-infra/jenkins/job_LoadTests_SideInput_Python.groovy

Line 120 in 5e38dec

name: '1gb-1kb-10workers-1000window-1key-percent-dict',

Test Dashboard - http://metrics.beam.apache.org/d/-E9aGlFGk/side-input-load-tests?orgId=1&from=now-90d&to=now&viewPanel=8

timestamp: Sat Jan  6 18:15:27 2024, metric_value: 100.00
timestamp: Fri Jan  5 18:34:45 2024, metric_value: 138.00
timestamp: Thu Jan  4 18:24:31 2024, metric_value: 580.00 <---- Anomaly
timestamp: Wed Jan  3 18:21:10 2024, metric_value: 92.00
timestamp: Tue Jan  2 18:19:11 2024, metric_value: 102.00
timestamp: Mon Jan  1 18:16:00 2024, metric_value: 82.00
timestamp: Sun Dec 31 18:14:10 2023, metric_value: 99.00
timestamp: Sat Dec 30 18:13:33 2023, metric_value: 105.00
timestamp: Fri Dec 29 18:31:15 2023, metric_value: 81.00
timestamp: Thu Dec 28 18:34:55 2023, metric_value: 78.00
timestamp: Wed Dec 27 18:13:18 2023, metric_value: 101.00
timestamp: Tue Dec 26 18:13:27 2023, metric_value: 95.00
timestamp: Mon Dec 25 18:15:10 2023, metric_value: 85.00

[AnandInguva]

#29943 and #29944 seems to way random in values. I think these tests are not adding any value in determining a performance regression.

I think we should remove these tests from the perf test config file.

[damccorm]

@AnandInguva it seems like outside of this one anomaly (which I'm guessing was bad hardware or something and is pretty easy to discard) this has been pretty stable - my vote would be to close/ignore this issue but leave the tests