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 vstinner
Recipients gvanrossum, neologix, vstinner
Date 2014-02-07.16:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391791172.15.0.661382377277.issue20505@psf.upfronthosting.co.za>
In-reply-to
Content
"If you want to keep the current approach, nothing prevents from using a
fixed "slack" value, independant of the selector (e.g. 1ms seems
reasonable)."

select() and kqueue() are able to sleep less than 1 ms. Using a slack of 1 ms would reduce the accuracy. I don't see why we should limit the accuracy. Why 1 ms? Because of poll/epoll? What about Windows and its resolution of 15.6 ms?

Well, under 1 ms, don't expect accurate results :-) For example on my fast Linux box, a select() with a timeout of 61 us takes 137 us (elapsed time measued in Python).
History
Date User Action Args
2014-02-07 16:39:32vstinnersetrecipients: + vstinner, gvanrossum, neologix
2014-02-07 16:39:32vstinnersetmessageid: <1391791172.15.0.661382377277.issue20505@psf.upfronthosting.co.za>
2014-02-07 16:39:32vstinnerlinkissue20505 messages
2014-02-07 16:39:31vstinnercreate