Run usage data calculations in separate queue #2681
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.
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:
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.
The text was updated successfully, but these errors were encountered: