jingrow/gunicorn
1
0
Fork 0
mirror of https://github.com/frappe/gunicorn.git synced 2026-01-14 11:09:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc: Notes about worker keepalive support

Browse Source
This commit is contained in:
Tuukka Mustonen 2017-06-15 20:10:06 +03:00 committed by Berker Peksag
parent fc0d973416
commit 0e4e0779e6
3 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/design.rst
View File

@ -34,6 +34,10 @@ as any errors will affect at most a single request. Though as we describe below
only processing a single request at a time requires some assumptions about how only processing a single request at a time requires some assumptions about how
applications are programmed. applications are programmed.
``sync`` worker does not support persistent connections - each connection is
closed after response has been sent (even if you manually add ``Keep-Alive``
or ``Connection: keep-alive`` header in your application).
Async Workers Async Workers
------------- -------------

9
docs/source/settings.rst
View File

@ -234,7 +234,14 @@ keepalive
The number of seconds to wait for requests on a Keep-Alive connection. The number of seconds to wait for requests on a Keep-Alive connection.
Generally set in the 1-5 seconds range. Generally set in the 1-5 seconds range for servers with direct connection
to the client (e.g. when you don't have separate load balancer). When
Gunicorn is deployed behind a load balancer, it often makes sense to
set this to a higher value.
.. note::
``sync`` worker does not support persistent connections and will
ignore this option.
Security Security
-------- --------

9
gunicorn/config.py
View File

@ -760,7 +760,14 @@ class Keepalive(Setting):
desc = """\ desc = """\
The number of seconds to wait for requests on a Keep-Alive connection. The number of seconds to wait for requests on a Keep-Alive connection.
Generally set in the 1-5 seconds range. Generally set in the 1-5 seconds range for servers with direct connection
to the client (e.g. when you don't have separate load balancer). When
Gunicorn is deployed behind a load balancer, it often makes sense to
set this to a higher value.
.. note::
``sync`` worker does not support persistent connections and will
ignore this option.
""" """