summaryrefslogtreecommitdiffstats
path: root/doc/server
diff options
context:
space:
mode:
authorChris St. Pierre <chris.a.st.pierre@gmail.com>2014-01-27 09:04:11 -0500
committerChris St. Pierre <chris.a.st.pierre@gmail.com>2014-01-27 09:04:33 -0500
commitaf0187c69a933c83d08760d251c1284dcdc3d5fe (patch)
tree07905abbd14c2af95d23eb80a5f4857ddfd83254 /doc/server
parent1e2c612e336e87972d6f2713ebf477df79fe8440 (diff)
downloadbcfg2-af0187c69a933c83d08760d251c1284dcdc3d5fe.tar.gz
bcfg2-af0187c69a933c83d08760d251c1284dcdc3d5fe.tar.bz2
bcfg2-af0187c69a933c83d08760d251c1284dcdc3d5fe.zip
doc: added multiprocessing core docs, including tmpwatch fix
Diffstat (limited to 'doc/server')
-rw-r--r--doc/server/configuration.txt43
1 files changed, 43 insertions, 0 deletions
diff --git a/doc/server/configuration.txt b/doc/server/configuration.txt
index bb4983367..383367a46 100644
--- a/doc/server/configuration.txt
+++ b/doc/server/configuration.txt
@@ -218,3 +218,46 @@ To select which backend to use, set the ``backend`` option in the
* ``best`` (the default; currently the same as ``builtin``)
``best`` may change in future releases.
+
+Multiprocessing core configuration
+----------------------------------
+
+If you use the multiprocessing core, there are other bits you may wish
+to twiddle.
+
+By default, the server spawns as many children as the host has CPUs.
+(This is determined by ``multiprocessing.cpu_count()``.) To change
+this, set:
+
+.. code-block:: conf
+
+ [server]
+ children = 4
+
+The optimal number of children may vary depending on your workload.
+For instance, if you are using :ref:`native yum
+library support <native-yum-libraries>`, then a separate process is
+spawned for each client to resolve its package dependencies, so
+keeping the children at or below the CPU count is likely a good idea.
+If you're not using native yum library support, though, you may wish
+to oversubscribe the core slightly. It's recommended that you test
+various configurations and use what works best for your workload.
+
+Secondly, if ``tmpwatch`` is enabled, you must either disable it or
+exclude the pattern ``/tmp/pymp-\*``. For instance, on RHEL or CentOS
+you may have a line like the following in
+``/etc/cron.daily/tmpwatch``:
+
+.. code-block:: bash
+
+ /usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix \
+ -x /tmp/.ICE-unix -x /tmp/.Test-unix 240 /tmp
+
+You would need to add ``-X /tmp/pymp-\*`` to it, like so:
+
+.. code-block:: bash
+
+ /usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix \
+ -x /tmp/.ICE-unix -x /tmp/.Test-unix -X /tmp/pymp-\* 240 /tmp
+
+See https://bugzilla.redhat.com/show_bug.cgi?id=1058310 for more information.