From b3f1c5cc29db4f25fd9dc239f84af0c133b73a41 Mon Sep 17 00:00:00 2001 From: John Bachir Date: Sun, 31 Jul 2016 00:59:30 -0400 Subject: [PATCH] clarify language regarding undefined time tasks (#1316) --- docs/source/design.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/source/design.rst b/docs/source/design.rst index f4f21603..9350c18b 100644 --- a/docs/source/design.rst +++ b/docs/source/design.rst @@ -65,12 +65,13 @@ The worker `gaiohttp` is a full asyncio worker using aiohttp_. Choosing a Worker Type ====================== -The default synchronous workers assume that your application is resource bound +The default synchronous workers assume that your application is resource-bound in terms of CPU and network bandwidth. Generally this means that your -application shouldn't do anything that takes an undefined amount of time. For -instance, a request to the internet meets this criteria. At some point the -external network will fail in such a way that clients will pile up on your -servers. +application shouldn't do anything that takes an undefined amount of time. An example +of something that takes an undefined amount of time is a request to the internet. +At some point the external network will fail in such a way that clients will pile up on your +servers. So, in this sense, any web application which makes outgoing requests to +APIs will benefit from an asynchronous worker. This resource bound assumption is why we require a buffering proxy in front of a default configuration Gunicorn. If you exposed synchronous workers to the