From 712a502d6263b8da44b32694f7f761152bb9524f Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Thu, 22 Dec 2016 22:00:46 +0300 Subject: [PATCH] Cleanup trailing whitespaces --- docs/source/faq.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/source/faq.rst b/docs/source/faq.rst index e2043378..1febae65 100644 --- a/docs/source/faq.rst +++ b/docs/source/faq.rst @@ -166,17 +166,17 @@ With asynchronous workers, creating URLs with the ``reverse`` function of How do I avoid Gunicorn excessively blocking in ``os.fchmod``? -------------------------------------------------------------- -The current heartbeat system involves calling ``os.fchmod`` on temporary file -handlers and may block a worker for arbitrary time if the directory is on a -disk-backed filesystem. For example, by default ``/tmp`` is not mounted as -``tmpfs`` in Ubuntu; in AWS an EBS root instance volume may sometimes hang for -half a minute and during this time Gunicorn workers may completely block in -``os.fchmod``. ``os.fchmod`` may introduce extra delays if the disk gets full. -Also Gunicon may refuse to start if it can't create the files when the disk is +The current heartbeat system involves calling ``os.fchmod`` on temporary file +handlers and may block a worker for arbitrary time if the directory is on a +disk-backed filesystem. For example, by default ``/tmp`` is not mounted as +``tmpfs`` in Ubuntu; in AWS an EBS root instance volume may sometimes hang for +half a minute and during this time Gunicorn workers may completely block in +``os.fchmod``. ``os.fchmod`` may introduce extra delays if the disk gets full. +Also Gunicon may refuse to start if it can't create the files when the disk is full. -Currently to avoid these problems you can create a ``tmpfs`` mount (for a new -directory or for ``/tmp``) and pass its path to ``--worker-tmp-dir``. First, +Currently to avoid these problems you can create a ``tmpfs`` mount (for a new +directory or for ``/tmp``) and pass its path to ``--worker-tmp-dir``. First, check whether your ``/tmp`` is disk-backed or RAM-backed:: $ df /tmp