Message179157
In issue #16853, it was noted that many several projects don't set epoll.poll() maxevents argument, which effectively limits the number of events retuend to FD_SETSIZE-1 (set in selectmodule.c).
Also, the methode documentation can confuse users into thinking that by default, the number of events is unlimited:
"""
.. method:: epoll.poll(timeout=-1, maxevents=-1)
Wait for events. timeout in seconds (float)
"""
It would probably make sense to use a larger default value for epoll max events (the only downside is increased memory consumption for the events array), maybe based on RLIMIT_NOFILE hard limit.
And the documentation should probably be improved. |
|
Date |
User |
Action |
Args |
2013-01-06 00:33:24 | neologix | set | recipients:
+ neologix |
2013-01-06 00:33:24 | neologix | set | messageid: <1357432404.49.0.731162769858.issue16873@psf.upfronthosting.co.za> |
2013-01-06 00:33:24 | neologix | link | issue16873 messages |
2013-01-06 00:33:24 | neologix | create | |
|