From 604284ea4c33998676bc42e1c23ee94d0c55d87c Mon Sep 17 00:00:00 2001 From: Clement Verna Date: Tue, 19 Mar 2019 11:39:21 +0100 Subject: [PATCH] Badges: Give fedbadges consumer 3 threads. Some of fedbages query to datanommer are really slow, that makes the consumer enable to catch up with all the messages on the bus Giving it 2 more threads improves the situation. Signed-off-by: Clement Verna --- roles/badges/backend/templates/badges-awarder.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/roles/badges/backend/templates/badges-awarder.py b/roles/badges/backend/templates/badges-awarder.py index 81c4af445f..cff12a91cc 100644 --- a/roles/badges/backend/templates/badges-awarder.py +++ b/roles/badges/backend/templates/badges-awarder.py @@ -2,9 +2,7 @@ config = { # We need to tell the fedmsg-hub that it should load our consumer on start. "fedmsg.consumers.badges.enabled": True, - # fedbadges only needs 1 thread. It is fast enough as is and the multiple - # threads tend to get themselves into database deadlocks. - "moksha.workers_per_consumer": 1, + "moksha.workers_per_consumer": 3, "moksha.threadpool_size": 4, # This tells the consumer where to look for its BadgeRule definitions. It