This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lguo
Recipients lguo
Date 2018-06-08.22:53:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528498427.18.0.592728768989.issue33811@psf.upfronthosting.co.za>
In-reply-to
Content
https://bugs.python.org/issue27906 describes a situation where accept rate of connection is too slow for use cases where spikes of incoming connection warrants fast accept. The fix for that was to accept socket connection in a tight loop until it reaches "backlog" connections.

This doesn't work very well in a web server scenario where we have many processes listening on the same socket. Each process should not accept up to "backlog" connections, for better load balancing among processes. It would be ideal if this is a separate argument for the server configuration so that the application can decide up to how many connections it is willing to accept in the loop, independent of the backlog parameter for listen() system call.

Let me know if this makes sense.

Lisa
History
Date User Action Args
2018-06-08 22:53:47lguosetrecipients: + lguo
2018-06-08 22:53:47lguosetmessageid: <1528498427.18.0.592728768989.issue33811@psf.upfronthosting.co.za>
2018-06-08 22:53:47lguolinkissue33811 messages
2018-06-08 22:53:47lguocreate