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 yselivanov
Recipients Liran Nuna, serhiy.storchaka, yselivanov
Date 2017-12-05.03:47:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512445670.86.0.213398074469.issue32204@psf.upfronthosting.co.za>
In-reply-to
Content
> I agree that the PR I offers little (or no) improvement but I implore you to explore performance bottlenecks in async/await.

And I'm saying that there are no "performance bottlenecks in async/await".  async/await is *not* asyncio.  async/await and yield are language constructs that use generator objects.

Your benchmark *does not* test async/await vs yield.  It compares asyncio.gather to batches in asynq.

Now, maybe asyncio.gather can be optimized, but we should open a separate issue for that if we can have a better implementation of it.

Your benchmark doesn't test the performance of IO -- that's the thing we actually optimize in asyncio and that we usually benchmark.  asyncio.gather is a niche thing, and usually network applications don't have it as a bottleneck.

Closing this issue.
History
Date User Action Args
2017-12-05 03:47:50yselivanovsetrecipients: + yselivanov, serhiy.storchaka, Liran Nuna
2017-12-05 03:47:50yselivanovsetmessageid: <1512445670.86.0.213398074469.issue32204@psf.upfronthosting.co.za>
2017-12-05 03:47:50yselivanovlinkissue32204 messages
2017-12-05 03:47:50yselivanovcreate