From 3fa7af52ba0c8847eeed8944c6f1f711e71d60d3 Mon Sep 17 00:00:00 2001 From: Johannes Date: Tue, 22 Nov 2011 15:54:15 +0000 Subject: Fix heading grammar --- docs/async.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/async.rst b/docs/async.rst index 522e63e..e991d35 100644 --- a/docs/async.rst +++ b/docs/async.rst @@ -12,7 +12,7 @@ Simple enough, but there is a snag: All this happens synchronously. If your appl Most servers limit the number of threads to avoid their relatively high overhead. Pools of 20 or less threads are common. As soon as all threads are occupied, any new connection is stalled. The server is effectively dead for everyone else. If you want to implement a chat that uses long-polling ajax requests to get real-time updates, you'd reach the limited at 20 concurrent connections. That's a pretty small chat. -Greenlets for the rescue +Greenlets to the rescue ------------------------ Most servers limit the size of their worker pools to a relatively low number of concurrent threads, due to the high overhead involved in switching between and creating new threads. While threads are cheap compared to processes (forks), they are still expensive to create for each new connection. -- cgit v1.2.1