aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDaniel Schadt <kingdread@gmx.de>2023-04-26 17:56:57 +0200
committerDaniel Schadt <kingdread@gmx.de>2023-04-26 17:56:57 +0200
commitf7fce26deacf8b63b4852c511eb9cf460df694f9 (patch)
tree996f73110fc0c3b53fbd38983d64eacd25a0f0fe /doc
parentbed7fb49b476db831c8d65ea1689ee89b9a0e369 (diff)
downloadfietsboek-f7fce26deacf8b63b4852c511eb9cf460df694f9.tar.gz
fietsboek-f7fce26deacf8b63b4852c511eb9cf460df694f9.tar.bz2
fietsboek-f7fce26deacf8b63b4852c511eb9cf460df694f9.zip
allow number of hittekaart threads to be limited
Diffstat (limited to 'doc')
-rw-r--r--doc/administration/configuration.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/administration/configuration.rst b/doc/administration/configuration.rst
index d272234..5be3537 100644
--- a/doc/administration/configuration.rst
+++ b/doc/administration/configuration.rst
@@ -227,6 +227,12 @@ empty, which means that Fietsboek will not generate any overlays on its own.
You can add ``heatmap`` and/or ``tilehunter`` to generate those maps
automatically.
+By default, ``hittekaart`` will use as many threads as CPU cores are available.
+This leads to the fastest heatmap generation, but might be undesired on shared
+hosts that also have other services running. You can explicitely set a thread
+count by setting ``hittekaart.threads``. A value of "0" is equivalent to the
+default behavior.
+
.. note::
The ``hittekaart.autogenerate`` has no effect on the ``fietsctl
@@ -245,5 +251,6 @@ An example configuration excerpt can look like this:
hittekaart.bin = /usr/local/bin/hittekaart
hittekaart.autogenerate = heatmap tilehunter
+ hittekaart.threads = 2
.. _hittekaart: https://gitlab.com/dunj3/hittekaart