➜

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 asvetlov, decaz, yselivanov
Date 2018-03-22.18:06:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521741961.59.0.467229070634.issue33115@psf.upfronthosting.co.za>
In-reply-to
Content 
> Does this mean that GC uses most part of CPU time so the loop blocks?

GC stops all Python code in the OS process from running.  Because of the GIL code in threads will obviously be stopped too.  This is true for both CPython and PyPy at this moment.

> And another question: do you have any plans to optimize the loop so it would be possible to run really lot of tasks in parallel?

The only way of doing this is to have a few asyncio OS processes (because of the GIL we can't implement M:N scheduling in a single Python process).  So it's not going to happen in the foreseeable future :(
History
Date User Action Args
2018-03-22 18:06:01yselivanovsetrecipients: + yselivanov, asvetlov, decaz
2018-03-22 18:06:01yselivanovsetmessageid: <1521741961.59.0.467229070634.issue33115@psf.upfronthosting.co.za>
2018-03-22 18:06:01yselivanovlinkissue33115 messages
2018-03-22 18:06:01yselivanovcreate