Epic: Performance metrics/milestones for profiling and optimisation of workspace loading

[loujaybee]

Often users ask us about performance issues, however Gitpod has many aspects that load when a workpace loads:

1. Fetching of base image
2. Starting workspace
3. Starting IDE
4. Starting terminal processess etc

However, there is no holistic way for a user or operator of Gitpod to optimise their setup across these phases. Additionally, there is currently no way to get visibility into a workspace performance issue if the workspace itself is unresponsive.

Relates to:

• Epic: In product collection of workspace logs #10802
• https://github.com/gitpod-io/website/issues/2246
• Display ETA and details when starting a workspace #3738
• Show prebuild logs for all tasks #9994

This epic would be to:

1. Define these key "loading" milestones in Gitpod (end-to-end)
2. Expose this information somewhere to the user so they can: debug + optimise their Gitpod workspace loading

(internal info)

[loujaybee]

CC: @lucasvaltl - I see this as a tool for the installer persona.
CC: @atduarte - Likely a big overlap with workspaces.
CC: @Furisto - Because of: https://github.com/gitpod-io/ops/issues/3070

See also internal conversation.

[loujaybee]

Linking related comment about loading milestones as user feedback for the case of supporting onboarding:

One idea for if you make it a more first-class feature -- something like a status page where you could update it dynamically. So it could contain basic Welcome/Getting Started content, but also configurable checkboxes: like 1) Seeding database with test data, 2) Compiling static assets, 3) Setting default settings, etc. Then, as the gitpod startup script executes, you can call gp checklist db-seed to mark something as done. Then the user has an idea via the UI of what's happening. Then the final step could be 4) Visit your test site, where you could push it a value that is from gp url 8080 (source)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.