Right now we lump all celery tasks into a single worker, but there are now many slower tasks for fetching jetstream/monitoring data that run frequently, and also the tasks that just broker interactions with Remote Settings. Let's split those out so we have two workers: one dedicated to RS changes, and one that handles the slower moving jobs. That way a slow moving job doesn't block fast turn around for RS reviews.
┆Issue is synchronized with this Jira Task
Right now we lump all celery tasks into a single worker, but there are now many slower tasks for fetching jetstream/monitoring data that run frequently, and also the tasks that just broker interactions with Remote Settings. Let's split those out so we have two workers: one dedicated to RS changes, and one that handles the slower moving jobs. That way a slow moving job doesn't block fast turn around for RS reviews.
┆Issue is synchronized with this Jira Task