Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-416

Limiting GraalVM memory usage relying on container cgroups

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Minor
    • 1.12.0.Final
    • 0.5.0
    • Image
    • None

    Description

      Today we're relying on LIMIT_MEMORY environment variable to set the JVM max memory usage for native builds.

      This seems to not be the better way of achieving this since we're relying on environment variables set by the operator. Ideally, would be better to not rely on the operator and limiting the way each other is interconnected.

      This article can be a good source of information:
      https://medium.com/@asishrs/docker-limit-resource-utilization-using-cgroup-parent-72a646651f9d

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-417 Remove LIMIT_MEMORY and LIMIT_CPU environment variable from s2i BuildConfig

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-419 When building native applications, builder pods get OOMKilled

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-306 Limiting GraalVM memory usage on Quarkus s2i images builds

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rhn-support-fspolti Filippe Spolti
              rhn-support-zanini Ricardo Zanini Fernandes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: