Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1200

SBO memory usage is increased significantly on OCP 4.11 compared to 4.10

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide
      Currently, when you install {servicebinding-title} on {product-title} 4.11, the memory footprint of {servicebinding-title} increases beyond expected limits. With low usage, however, the memory footprint stays within the expected ranges of your environment or scenarios. In comparison with {product-title} 4.10, under stress, both the average and maximum memory footprint increase considerably. This issue is evident in the previous versions of {servicebinding-title} as well. There is currently no workaround for this issue.
      Show
      Currently, when you install {servicebinding-title} on {product-title} 4.11, the memory footprint of {servicebinding-title} increases beyond expected limits. With low usage, however, the memory footprint stays within the expected ranges of your environment or scenarios. In comparison with {product-title} 4.10, under stress, both the average and maximum memory footprint increase considerably. This issue is evident in the previous versions of {servicebinding-title} as well. There is currently no workaround for this issue.
    • AppSvc Sprint 225

    Description

      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

      Attachments

        Issue Links

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: APPSVC

              People

                pmacik@redhat.com Pavel Macik
                pmacik@redhat.com Pavel Macik
                Andy Sadler
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated: