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.

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

Run usage data calculations in separate queue #2681

Open
lbarcziova opened this issue Dec 12, 2024 · 0 comments
Open

Run usage data calculations in separate queue #2681

lbarcziova opened this issue Dec 12, 2024 · 0 comments
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lbarcziova
Copy link
Member

As we discussed with the team in our architecture meeting, calculations of the usage statistics are resource-demanding and can block multiple workers (even all), mainly on startup (redeployment), when no data is cached yet. We should avoid this, most probably by having a separate queue where those tasks would be run.

Other alternatives that can be considered:

  • utilising task priorities
  • cronjobs

When discussing this issue, we also touched on the topic of the data cleanup that might be needed, we should think about that as well.

@lbarcziova lbarcziova added kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. complexity/single-task Regular task, should be done within days. area/other Related to some other area/category than the specified ones. labels Dec 12, 2024
@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: priority-backlog
Development

No branches or pull requests

1 participant