[JetBrains] Show Workspace CPU/Memory resources in control center

[andreafalzetti]

Context

Currently, in JetBrains IDE the CPU/Memory usage displayed applies to the whole node, instead of displaying the workspace's specific resources.

Description

With this PR we introduce two additional progress bars at the top displaying:

• Workspace CPU
• Workspace Memory

Please note: The Unit used for Memory resource is on purpose "GB" instead of "Mi" like in gitpod-cli, my reasons:

1. personally I find it shorter and easier to read 0.38GB / 1.55GB instead of 2944Mi/11870Mi
2. when talking about memory (in general) it's more common to refer to GB
3. in gitpod.io our memory (especially for XL) can be a large number to read if it's in Mi

I would actually like to propose a separate issue to change it also in gp top but I would like to know if there are any reasons or string objections in favor of the smaller unit. cc @akosyakov @felladrin

Related Issue(s)

Fixes #10580

How to test

1. Signup to this prev env
2. Select IntelliJ + Latest Release (Unstable) as your preferred IDE
3. Start a workspace for https://github.com/gitpod-io/spring-petclinic
4. Click on the control center and see available resources, notice the additional rows at the top (Workspace CPU/Memory) before the default CPU/Memory

OPTIONAL:

9. To stress the CPU, run: yes > /dev/null & multiple times, observe the progress bar growing and moving to Warning and Danger.
10. To get the CPU back to a lower value, run: killall yes
11. To stress the Memory, run cat /dev/zero | head -c 5G | tail once or twice, and observe the memory progress bar behaving as expected

Release Notes

JetBrains: Display Workspace CPU/Memory usage in Backend Control Center

Documentation

Werft options:

• /werft with-preview

[werft-gitpod-dev-com]

started the job as gitpod-build-afalz-10580-show-workspace-metrics-in-jb-cont.5 because the annotations in the pull request description changed
(with .werft/ from main)

[akosyakov]

code wise it looks good, but i did not try, i wanted but it was pretty slow, probably someone else already trying :D

/hold
hold just in case if someone wants to try or Andrea wants to address something else

[akosyakov]

I would actually like to propose a separate issue to change it also in gp top but I would like to know if there are any reasons or string objections in favor of the smaller unit. cc @akosyakov @felladrin

I think it should be aligned with default of standard tools like top or htop.

[andreafalzetti]

I think it should be aligned with default of standard tools like top or htop.

It's an interesting take, to look at htop or top - I had a look as I didn't remember what unit the use; for memory htpp also uses G / GB, while top uses M 😄

[felladrin]

I would actually like to propose a separate issue to change it also in gp top but I would like to know if there are any reasons or string objections in favor of the smaller unit. cc @akosyakov @felladrin

For me, it's also nicer to have it in "GB".

[felladrin]

ℹ️ I'm reviewing it now.

[felladrin]

Working great! ✅

[andreafalzetti]

Thanks @felladrin and @akosyakov 🙌

/unhold

[akosyakov]

For me, it's also nicer to have it in "GB".

let's go with GB then