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 Manjusaka
Recipients Manjusaka, giampaolo.rodola, neologix, vstinner, yselivanov
Date 2018-12-17.11:09:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545044942.1.0.788709270274.issue35517@psf.upfronthosting.co.za>
In-reply-to
Content
Hello rodola

Here's detail:

In the server, we use multiprocess to handle the request with share the same FD. 

OK, when a request comes, all the process wake up and try to accept the request but only one process will accept success and the others will raise an Exception if we use the epoll without EPOLLEXCLUSIVE.

That means there will waste the performance. This effect is named thundering herd.

But if we use epoll with EPOLLEXCLUSIVE, when the envents happen, only one process will wake and try to handle the event.

So, I think it's necessary to support the EPOLLEXCLUSIVE in selectors.EpollSelector

Actually, Python support EPOLLEXCLUSIVE official since 3.7. It's time to support it in selectors
History
Date User Action Args
2018-12-17 11:09:02Manjusakasetrecipients: + Manjusaka, vstinner, giampaolo.rodola, neologix, yselivanov
2018-12-17 11:09:02Manjusakasetmessageid: <1545044942.1.0.788709270274.issue35517@psf.upfronthosting.co.za>
2018-12-17 11:09:02Manjusakalinkissue35517 messages
2018-12-17 11:09:01Manjusakacreate