From 854283c2e5e1811ccefc5d7155557f5764886aa3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wxcaf=C3=A9=20=28Cl=C3=A9ment=20Hertling=29?= <wxcafe@wxcafe.net> Date: Thu, 12 Jul 2018 21:11:23 +0200 Subject: [PATCH] fixed your->you're, reformatted paragraphs --- docs/installation/optimization.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/installation/optimization.rst b/docs/installation/optimization.rst index f873795e..9ff8ffad 100644 --- a/docs/installation/optimization.rst +++ b/docs/installation/optimization.rst @@ -2,7 +2,7 @@ Optimizing your Funkwhale instance ================================== Depending on your requirements, you may want to reduce as much as possible -Funkwhale's footprint. +Funkwhale's memory footprint. Reduce workers concurrency -------------------------- @@ -14,9 +14,9 @@ memory usage. You can control this behaviour using the ``--concurrency`` flag. For instance, setting ``--concurrency=1`` will spawn only one worker. -This flag should be appended after the ``celery -A funkwhale_api.taskapp worker`` -command in your :file:`docker-compose.yml` file if your using Docker, or in your -:file:`/etc/systemd/system/funkwhale-worker.service` otherwise. +This flag should be appended after the ``celery -A funkwhale_api.taskapp +worker`` command in your :file:`docker-compose.yml` file if your using Docker, +or in your :file:`/etc/systemd/system/funkwhale-worker.service` otherwise. .. note:: @@ -33,5 +33,5 @@ Using the ``solo`` pool type should reduce your memory consumption. You can control this behaviour using the ``--pool=solo`` flag. This flag should be appended after the ``celery -A funkwhale_api.taskapp worker`` -command in your :file:`docker-compose.yml` file if your using Docker, or in your -:file:`/etc/systemd/system/funkwhale-worker.service` otherwise. +command in your :file:`docker-compose.yml` file if you're using Docker, or in +your :file:`/etc/systemd/system/funkwhale-worker.service` otherwise. -- GitLab