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 giampaolo.rodola
Recipients William.Edwards, giampaolo.rodola, sbt
Date 2012-10-17.22:34:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350513289.76.0.255329949396.issue16269@psf.upfronthosting.co.za>
In-reply-to
Content
On one hand this seems reasonable to me, on the other hand I'm not sure.
select() other than being supported on all platforms has the advantage of being simple and quick to use (you just call it once by passing a set of fds and then you're done).

poll() / epoll() aren't as simple as they require:

- e/poll() object initialization
- fds registration 
- fds unregistration
- e/poll() object destruction

Given the exact point where this is supposed to take place (here: http://hg.python.org/cpython/file/f6fcff683866/Lib/multiprocessing/connection.py#l865) I'm not sure it's really worth the effort as on one hand you fix a pretty rare scalability issue, on the other hand you introduce a considerable slowdown given the amount of operations involved and described above.
History
Date User Action Args
2012-10-17 22:34:49giampaolo.rodolasetrecipients: + giampaolo.rodola, sbt, William.Edwards
2012-10-17 22:34:49giampaolo.rodolasetmessageid: <1350513289.76.0.255329949396.issue16269@psf.upfronthosting.co.za>
2012-10-17 22:34:49giampaolo.rodolalinkissue16269 messages
2012-10-17 22:34:49giampaolo.rodolacreate