[Python-Dev] Reworking the GIL (original) (raw)
Daniel Stutzbach daniel at stutzbachenterprises.com
Mon Oct 26 17🔞59 CET 2009
- Previous message: [Python-Dev] Reworking the GIL
- Next message: [Python-Dev] Reworking the GIL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Oct 26, 2009 at 10:58 AM, Antoine Pitrou <solipsis at pitrou.net>wrote:
Er, I prefer to keep things simple. If you have lots of I/O you should probably use an event loop rather than separate threads.
On Windows, sometimes using a single-threaded event loop is sometimes impossible. WaitForMultipleObjects(), which is the Windows equivalent to select() or poll(), can handle a maximum of only 64 objects.
Do we really need priority requests at all? They seem counter to your desire for simplicity and allowing the operating system's scheduler to do its work.
That said, if a thread's time budget is merely paused during I/O rather than reset, then a thread making frequent (but short) I/O requests cannot starve the system.
-- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20091026/c99a9f24/attachment.htm>
- Previous message: [Python-Dev] Reworking the GIL
- Next message: [Python-Dev] Reworking the GIL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]