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 scoder
Recipients brett.cannon, gregory.p.smith, pitrou, scoder
Date 2013-10-13.07:30:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Another thing: you are only using one thread for both the client and the server, and the app writes the entire content in one go (during one call to get()). Wouldn't it be more interesting to make the app's get() method asynchronous as well, so that each chunk actually gets passed separately? Otherwise, the fact that it's writing chunks wouldn't really contribute all that much to the benchmark.

Or maybe split it up into two benchmarks, one that exercises the asynchronous client (as your current code does) and one that shifts more work to the server side? Not sure if it's worth it, but might be worth trying. I think it would cover two different use cases that way.
Date User Action Args
2013-10-13 07:30:28scodersetrecipients: + scoder, brett.cannon, gregory.p.smith, pitrou
2013-10-13 07:30:28scodersetmessageid: <>
2013-10-13 07:30:28scoderlinkissue19236 messages
2013-10-13 07:30:28scodercreate