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 neologix
Recipients giampaolo.rodola, josiah.carlson, josiahcarlson, neologix, pitrou, xdegaye
Date 2012-12-28.17:49:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM2JVGOHMdLaKh9pNe9Yr9DaNDUD=SBMjs-PcXgSsiG2hg@mail.gmail.com>
In-reply-to <1356715733.36.0.749982594979.issue16787@psf.upfronthosting.co.za>
Content
Alright, here's a simple patch bumping the buffers to 64K for asyncore
and asynchat.

> There is another problem with dispatcher_with_send: the buffering algorithm (both when appending and popping) is quadratic. You can easily observe it with your test script, when growing the DATA. async_chat looks much saner in that respect, I wonder why the same algorithm couldn't it be re-used.

Yeah, I noticed that.
But even in asynchat, there's a lot of copying going on, length
computations performed twice in a row, etc.

> (regardless, reading the asyncore code really hurts the eyes :-/)

Indeed.
Files
File name Uploaded
asyncore_buffsize.diff neologix, 2012-12-28.17:49:00
History
Date User Action Args
2012-12-28 17:49:01neologixsetrecipients: + neologix, josiahcarlson, pitrou, giampaolo.rodola, josiah.carlson, xdegaye
2012-12-28 17:49:01neologixlinkissue16787 messages
2012-12-28 17:49:00neologixcreate