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 Liran Nuna
Recipients Liran Nuna, serhiy.storchaka, yselivanov
Date 2017-12-05.03:12:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512443547.97.0.213398074469.issue32204@psf.upfronthosting.co.za>
In-reply-to
Content
> which makes them faster in some specific micro-benchmarks

I'm not talking about micro-benchmarks, we are actively using asynq in production. Recent efforts to migrate to async/await have hit a major  performance hit - our response times nearly doubled.

I agree that the PR I offers little (or no) improvement but I implore you to explore performance bottlenecks in async/await.
History
Date User Action Args
2017-12-05 03:12:28Liran Nunasetrecipients: + Liran Nuna, serhiy.storchaka, yselivanov
2017-12-05 03:12:27Liran Nunasetmessageid: <1512443547.97.0.213398074469.issue32204@psf.upfronthosting.co.za>
2017-12-05 03:12:27Liran Nunalinkissue32204 messages
2017-12-05 03:12:27Liran Nunacreate