Give bodhi2 backend another consumer thread.

inventory/group_vars/bodhi-backend

@@ -26,6 +26,8 @@ virt_install_command: virt-install -n {{ inventory_hostname }} -r {{ mem_size }}
 tcp_ports: [
     3000, 3001, 3002, 3003, 3004,
     3005, 3006, 3007, 3008, 3009,
+    3010, 3011, 3012, 3013, 3014,
+    3015, 3016, 3017, 3018, 3019,
 ]
 
 # With 16 cpus, theres a bunch more kernel threads

inventory/group_vars/bodhi-backend-stg

@@ -25,6 +25,8 @@ virt_install_command: virt-install -n {{ inventory_hostname }} -r {{ mem_size }}
 tcp_ports: [
     3000, 3001, 3002, 3003, 3004,
     3005, 3006, 3007, 3008, 3009,
+    3010, 3011, 3012, 3013, 3014,
+    3015, 3016, 3017, 3018, 3019,
 ]
 
 # With 16 cpus, theres a bunch more kernel threads

roles/bodhi2/base/tasks/main.yml

@@ -67,6 +67,7 @@
       mode=0644
   with_items:
   - bodhi-logging.py
+  - bodhi-threading.py
   - bodhi.py
   - masher.py
   notify:

roles/bodhi2/base/templates/bodhi-threading.py

@@ -0,0 +1,10 @@
+config = {
+    # This sets uptwo master threads to handle incoming messages.
+    # Each of those master consumer threads then can fork off many masher
+    # threads to mash different repos.
+    # If you crank up this number, you should also crank up:
+    # - the iptables rules in inventory/group_vars/bodhi-backend
+    # - the fedmsg endpoints in roles/fedmsg/base/templates/endpoints-bodhi.py
+    "moksha.workers_per_consumer": 2,
+    "moksha.threadpool_size": 22,
+}

roles/fedmsg/base/templates/endpoints-bodhi.py.j2

@@ -9,12 +9,12 @@ config = dict(
     endpoints={
         "bodhi.bodhi-backend01": [
             "tcp://bodhi-backend01.%s:30%0.2i" % (suffix, i)
-            for i in range(10)
+            for i in range(20)
         ],
         {% if env != 'staging' %}
         "bodhi.bodhi-backend02": [
             "tcp://bodhi-backend02.%s:30%0.2i" % (suffix, i)
-            for i in range(10)
+            for i in range(20)
         ],
         {% endif %}
     }