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 <cverna@tutanota.com>
This commit is contained in:
parent
ab9b427ba9
commit
604284ea4c
1 changed files with 1 additions and 3 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue