Why traverse all fd instead of fd with data readable? Using "traverse all fd" strategy will lead to the following problems. When there are a large number of fd with no data readable in the m_destSockets queue, the sys cpu occupancy rate reaches 100%. #35

hougang2013 · 2019-06-16T10:11:56Z

hougang2013 · 2019-06-17T01:20:15Z

use RTPSession::DeleteDestination(RTPTCPAddress(sock_with_no_data_readable))
manually delete the fd with no data readable from the m_destSockets queue lead to sys cpu reduce to low rate!

j0r1 · 2019-09-01T13:34:19Z

How many destinations are you using at the same time?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Why traverse all fd instead of fd with data readable? Using "traverse all fd" strategy will lead to the following problems. When there are a large number of fd with no data readable in the m_destSockets queue, the sys cpu occupancy rate reaches 100%. #35

Why traverse all fd instead of fd with data readable? Using "traverse all fd" strategy will lead to the following problems. When there are a large number of fd with no data readable in the m_destSockets queue, the sys cpu occupancy rate reaches 100%. #35

hougang2013 commented Jun 16, 2019

hougang2013 commented Jun 17, 2019

j0r1 commented Sep 1, 2019

Why traverse all fd instead of fd with data readable? Using "traverse all fd" strategy will lead to the following problems. When there are a large number of fd with no data readable in the m_destSockets queue, the sys cpu occupancy rate reaches 100%. #35

Why traverse all fd instead of fd with data readable? Using "traverse all fd" strategy will lead to the following problems. When there are a large number of fd with no data readable in the m_destSockets queue, the sys cpu occupancy rate reaches 100%. #35

Comments

hougang2013 commented Jun 16, 2019

hougang2013 commented Jun 17, 2019

j0r1 commented Sep 1, 2019