Description of problem:

When installed on OCP 4.11, SBO memory footprint increases beyond expected limits. Under stress, both, the average and the max memory footprint increase considerably when compared with OCP 4.10. This behavior was discovered on 1.2 release but it is confirmed to also manifest on previous versions of SBO. If SBO is installed on OCP 4.11 with low usage the memory footprint will stay within expected ranges.

Prerequisites (if any, like setup, operators/versions):

OCP 4.11 cluster (This is the main change that triggers this issue OCP 4.10 does not show memory spikes)
SBO 1.2 (Can reproduce with previous versions on SBO)

Steps to Reproduce

1. Run our performance test on OCP 4.11 Cluster

Actual results:

Max memory utilization is close to 2Gigs

Expected results:

Max memory utilization is in the low Megs (less that 100)

Reproducibility: Always

Build Details:

When installed on OCP 4.11, SBO memory footprint increases beyond expected limits. Under stress, both, the average and the max memory footprint increase considerably when compared with OCP 4.10. This behavior was discovered on 1.2 release but it is confirmed to also manifest on previous versions of SBO. If SBO is installed on OCP 4.11 with low usage the memory footprint will stay within expected ranges.

Additional info:

Release Notes Type: Issue/Bug