From: Fabian Keil Date: Sat, 20 May 2017 09:25:14 +0000 (+0000) Subject: Add #158: Use a single thread to wait for new requests on reused client connections X-Git-Tag: v_3_0_27~165 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=390e98e99d8a401fa193a281a51e62c0cef13eb3;ds=sidebyside Add #158: Use a single thread to wait for new requests on reused client connections --- diff --git a/TODO b/TODO index 8eabebe1..56ef9901 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.161 2017/04/20 11:10:54 fabiankeil Exp $ +$Id: TODO,v 1.162 2017/05/20 09:25:00 fabiankeil Exp $ Some Privoxy-related tasks, sorted by the time they have been added, not by priority. @@ -471,6 +471,14 @@ http://www.privoxy.org/faq/general.html#DONATE 157) Add a directive to control the currently hardcoded receive-buffer size. +158) Use a single thread to wait for new requests on reused client connections. + Currently the thread that handles the first request on a connection + stays responsible for the client connect until it gets closed. + In case of lots of idle connections lots of waiting threads are used. + While it's conceivable that this ineffiency is irrelevant from a + performance point of view, using a single thread should reduce Privoxy's + memory footprint a bit which may be noticeable in case of multi-user setups + with hundreds of idle connections. ########################################################################## Hosting wish list (relevant for #53)