Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2589

Java plugin CPU limit is too low

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.15.0.GA
    • 2.15.0.GA
    • docs
    • False
    • False
    • Hide
      = Improved performance of the Java and Quarkus extensions for Visual Studio Code

      This enhancement improves the startup and runtime performance of the Java and Quarkus extensions for Visual Studio Code in workspaces that load Che-Theia with these extensions. The improved performance is achieved by increasing the CPU limit from 500 MB to 800 MB.
      Show
      = Improved performance of the Java and Quarkus extensions for Visual Studio Code This enhancement improves the startup and runtime performance of the Java and Quarkus extensions for Visual Studio Code in workspaces that load Che-Theia with these extensions. The improved performance is achieved by increasing the CPU limit from 500 MB to 800 MB.

      Synced from Eclipse Che issue

      https://github.com/eclipse/che/issues/20769

      Describe the bug

      The CPU used by Java vscode can go above 500m when activating.

      Che version

      7.36

      Steps to reproduce

      Start the Java Spring Boot sample on Developer Sandbox

      Expected behavior

      We should increase the CPU limit. Note that this is a limit, not a request. That means that if we set it too low there is a risk that the vscode extension will be throttled (will run much slower) but if we set it too high there are no risks except that the extension will be able to consume as much CPU as it needs (the pod is scheduled anyway, even if if the amount of CPU available is lower than the limit).

      Runtime

      OpenShift

      Screenshots

      No response

      Installation method

      other (please specify in additional context)

      Environment

      Dev Sandbox (workspaces.openshift.com)

      Release Notes Text

      Title: Java language support was slow due to low CPU limit
      Content: During startup and at runtime the Java language server was throttled because it required more CPU than the limit set by the container runtime. The CPU limit was increased from 500MB to 800MB.

            Unassigned Unassigned
            jiralint.codeready Bot Codeready
            Max Leonov Max Leonov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: