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

Optimize native build performed by OpenShift S2I

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 0.4.0
    • 0.2.0
    • Image
    • None
    • 2019 Week 38-40 (from Sep 16)

    Description

      Right now the Kogito native S2I build of OpenShift takes a significant amount of memory.
      Recent experiments showed that onboarding S2I build [1] can require more than 5GB of memory. Considering that there are no build pod limits defined this situation can lead to Out Of Memory issues on OpenShift node.

      Build pods should correctly handle their requirements or significantly reduce their resource usage.

      [1] https://github.com/kiegroup/kogito-examples/tree/master/onboarding-example/onboarding

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users KOGITO-305 Add an option to add a maven mirror URL through CLI/CR

          • 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.
          • Resolved

          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
          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-187 Allow jvm based build on Operator/CLI

          • 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

          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-186 Allow jvm based executable on runtime Quarkus image

          • 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.
          • Closed

          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-247 Improve Operator for Native build to enable quicker access

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: