improve connection polling

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47324

• Created at 2013-04-10 17:43:51 by lkrispen (@elkris)
• Closed as Fixed
• Assigned to lkrispen (@elkris)

---

If the number of concurrent established connections is high, the main thread, which polls all the active connections and iterates all the connections, can become a bottleneck.

Investigate alteratives, eg multiple polling threads, event completion frameworks ....

[389-ds-bot]

Comment from lkrispen (@elkris) at 2013-04-11 17:59:37

attachment
0001-multi-poll-part-1.patch

[389-ds-bot]

Comment from lkrispen (@elkris) at 2013-04-11 17:59:52

attachment
0002-multi-poll-part-2.patch

[389-ds-bot]

Comment from lkrispen (@elkris) at 2013-04-11 18:01:35

I did attach a port to current master of a fix provided by Nathan. Just for reference or as a starting point

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2015-03-10 23:10:27

nunc-stans is part of it - we still need to figure out how to do accept very fast - for the case where the server gets many new connection requests: Ticket 48121 - Accept many new connection requests (milestone - 1.3.5)

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2015-07-09 22:49:22

Per DS meeting on the 9th of July, closing this ticket as fixed.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 23:12:27

Metadata Update from @nhosoi:

• Issue assigned to elkris
• Issue set to the milestone: 1.3.4 backlog