Move some of Sidekiq workers to utilize database replicas
Move some of Sidekiq workers to utilize database replicas
This epic contains a list of issues that tracks Sidekiq workers that can be switched to utilize database replicas.
Impact | Worker | Owner Group | Done | Due Date |
---|---|---|---|---|
10 | BuildHooksWorker | ~"group::memory" | ![]() |
2021-05-11 |
8 | ExpirePipelineCacheWorker | ~"group::memory" | ![]() |
2021-06-17 |
8 | WebHookWorker | ~"group::memory" | ![]() |
2021-06-17 |
7 | PipelineHooksWorker | ~"group::memory" | ![]() |
2021-06-17 |
7 | BuildQueueWorker | ~"group::memory" | ![]() |
2021-06-17 |
5 | RequirementsManagement::ProcessRequirementsReportsWorker | groupproduct planning | ![]() |
2021-07-17 |
5 | PipelineNotificationWorker | grouppipeline execution | ![]() |
2021-10-17 |
3 | Deployments::HooksWorker | ~"group::release" | ![]() |
2021-08-17 |
3 | UpdateAllMirrorsWorker | groupsource code | ![]() |
2021-07-16 |
2 | JiraConnect::SyncBranchWorker | ~"group::ecosystem" | ![]() |
2021-07-16 |
2 | JiraConnect::SyncMergeRequestWorker | ~"group::ecosystem" | ![]() |
2021-07-16 |
2 | PipelineProcessWorker | ~"group::ecosystem" | ![]() |
2021-06-17 |
1 | Elastic::BulkCronWorker | groupglobal search | ![]() |
2021-05-12 |
Note:
-
The first column
Impact
indicates the impact. Higher number means bigger impact. -
Two metrics in this dashboard,
Sum of json.db_duration_s
andSum of json.db_primary_count
, are used to decide the weight.
- Show closed items
- View on a roadmap
- Show labels
- Show closed items
Link items together to show that they're related or that one is blocking others.