unable to comprehend the value shown as cpu metrics in theia-ide

[Divine1]

Summary

in theia-ide, cpu metrics shows Used 127895000m (used) / 500m (limited) . is the value shown here correct or incorrect?

i'm not able to comprehend the meaning of this value. i was expecting the value to be lessthan 500m.

My understanding is 500m implies 0.5core cpu

Relevant information

No response

[benoitf]

cc @svor

[svor]

It seems the bug on the resources monitor plugin side. Metrics server provides the value of used CPU in nanocores (nanoCPU) but the Resource Monitor displays this value with m (millicores/milliCPU).

@Divine1 could you please provide the information about the devfile and cluster which you use, because this problem is not reproducible on dogfooding instance with getting started samples.

[Divine1]

@svor thank you for the response. the cpu metric in nanocores makes sense.

i used below devfile.yaml , but i have removed the source code repo and image information. i used a java based project here(version jdk8). is this information sufficient?

schemaVersion: 2.1.0
metadata:
  name: cbfsel-repo
projects:
  - name: cbfsel-project
    git:
      checkoutFrom:
        revision: master
      remotes:
        origin: https://gitlab.org.com/cbf-sel.git
components:
  - container:
      image: 'internalOrganizationRepoDockerImage:jdk8img'
      memoryLimit: 4G
      endpoints:
        - exposure: public
          name: 4444-tcp
          protocol: tcp
          targetPort: 4444
        - exposure: public
          name: 5900-tcp
          protocol: tcp
          targetPort: 5900
        - exposure: public
          name: 7900-http
          protocol: http
          targetPort: 7900
          secure: true
      volumeMounts:
        - name: m2volume
          path: /home/user/.m2
    name: javacontainer
  - name: m2volume
    volume:
      size: 4G
commands:
  - exec:
      commandLine: mvn clean package -DskipTests
      component: javacontainer
      group:
        isDefault: true
        kind: build
      label: 'build project using maven'
      workingDir: '${PROJECT_SOURCE}'
    id: mvnpackage

[benoitf]

@Divine1 it might be interesting as well if you could provide the raw kubernetes metrics for this pod

(so we can see how it's reported)

[Divine1]

@benoitf

below is the raw k8s metric for the pod kubectl top pods -A

i have installed eclipseche in k8s cluster created via kubeadm.

@svor

[vitaliy-guliy]

@Divine1 is this bug still reproducible? I cannot create a workspace based on your devfile.

[Divine1]

@vitaliy-guliy this issue is fixed by @svor in #20809 i think, i will confirm once i check it. i will close this ticket for now.

need to update a valid container image in devfile.yaml to make it work.

[vitaliy-guliy]

I think this issue is a subtask of #20809

[svor]

It's still actual https://github.com/eclipse/che/issues/21683

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.