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

Research how to utilize Sentry's Performance to diagnose performance issues #2076

Open
4 tasks
jpopelka opened this issue Jun 1, 2023 · 1 comment
Open
4 tasks

Research how to utilize Sentry's Performance to diagnose performance issues #2076

jpopelka opened this issue Jun 1, 2023 · 1 comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@jpopelka
Copy link
Member

jpopelka commented Jun 1, 2023

Even after several investigations, we're still seeing intermittent SLO1 performance issues (#1954).
So far the identifications of the cause(s) have mostly been guesswork.

Luckily, we've been collecting performance data in Sentry since half of May.
They trace the transactions through the whole stack and should show us the bottlenecks more precisely.

For example this page shows the slowest task.steve_jobs.process_message transactions.

  • Study available resources (docs, videos) about how to utilize the Performance
  • Create a small demo for the team about what you've learned
  • Try to identify the causes of SLO1 performance issues
  • Update SLO1 performance issues #1954
@jpopelka jpopelka added complexity/single-task Regular task, should be done within days. impact/low This issue impacts only a few users. area/general Related to whole service, not a specific part/integration. gain/low This doesn't bring that much value to users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Jun 1, 2023
@nforro nforro moved this from new to backlog in Packit Kanban Board Jun 1, 2023
@lbarcziova
Copy link
Member

This is currently low prio, but we could have a look while working on #1954.

@lbarcziova lbarcziova mentioned this issue Jan 6, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpopelka @lbarcziova