You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that the parameter setting value in the file(session_p.h) is 5. What is the reason for this? Will there be any problems if a large number of devices are connected concurrently?
The text was updated successfully, but these errors were encountered:
Why the interest in a random internal macro, have you checked where it is used? In short, ignore it, it is extremely unlikely it will affect you in any way.
Why the interest in a random internal macro, have you checked where it is used? In short, ignore it, it is extremely unlikely it will affect you in any way.
The reason why I became interested in it is because we encountered the problem of tcp accept queue overflow. This parameter affects the size of the full connection queue, so I want to know what is the basis for setting this value?
I see, there is no special reason for the value. When implementing it (a long time ago) I saw 3 being used so I opted for a bit higher number to be safe. As long as you application is accepting new connections often enough, I do not think the queue can ever reach the limit.
I found that the parameter setting value in the file(session_p.h) is 5. What is the reason for this? Will there be any problems if a large number of devices are connected concurrently?
The text was updated successfully, but these errors were encountered: