Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[server] Monitor and optimize Workspace Start #8972

Open
Tracked by #8973
svenefftinge opened this issue Mar 28, 2022 · 2 comments
Open
Tracked by #8973

[server] Monitor and optimize Workspace Start #8972

svenefftinge opened this issue Mar 28, 2022 · 2 comments
Labels
aspect: performance anything related to performance component: server meta: never-stale This issue can never become stale operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@svenefftinge
Copy link
Member

This ticket is about running an optimization cycle (harvesting the top 3 performance improvements) for the workspace startup times between user sends request with context URL and ws-manager receives workspace spec.

Ideally, we introduce some observability metrics for this as well, so we can continuously monitor this.
Could be even a great long-standing success-criteria.
@svenefftinge svenefftinge mentioned this issue Mar 28, 2022
Closed
8 tasks
@geropl geropl added team: webapp Issue belongs to the WebApp team component: server operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) labels Apr 7, 2022
@geropl geropl moved this to Scheduled in 🍎 WebApp Team Apr 8, 2022
@geropl geropl removed the status in 🍎 WebApp Team Apr 14, 2022
@geropl geropl added the aspect: performance anything related to performance label Apr 14, 2022
@geropl geropl moved this to Scheduled in 🍎 WebApp Team Apr 26, 2022
@geropl geropl added the type: improvement Improves an existing feature or existing code label Apr 26, 2022
@AlexTugarev AlexTugarev self-assigned this Apr 27, 2022
@geropl geropl moved this from Scheduled to In Progress in 🍎 WebApp Team Apr 27, 2022
@geropl
Copy link
Member

geropl commented Apr 27, 2022

@AlexTugarev Moved to "In progess" based on your assignment 😉

@AlexTugarev AlexTugarev moved this from In Progress to Scheduled in 🍎 WebApp Team Jun 2, 2022
@geropl geropl removed the status in 🍎 WebApp Team Jul 11, 2022
@stale
Copy link

stale bot commented Sep 9, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 9, 2022
@stale stale bot closed this as completed Sep 25, 2022
@stale stale bot moved this to Done in 🍎 WebApp Team Sep 25, 2022
@geropl geropl added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Sep 26, 2022
@geropl geropl reopened this Sep 26, 2022
Repository owner moved this from Done to In Progress in 🍎 WebApp Team Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aspect: performance anything related to performance component: server meta: never-stale This issue can never become stale operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
🍎 WebApp Team
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
3 participants
@svenefftinge @AlexTugarev @geropl