We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
如题,不应该通过计算定期或者超时事件最小触发时间而动态进行设置吗? 无就绪事件而有定时器来时,4ms会有延迟处理; 无就绪事件也无定时器来时,4MS触发的往下执行没有必要。
The text was updated successfully, but these errors were encountered:
#31 (comment) 可以参考这个comment。 无就绪事件的情况下,即使timeout参数填0,也会等待4ms左右,所以4ms是可填的最小的参数。 为什么timeout参数要填最小的?是因为随时有就绪的resp需要通过active_socket_func_回传给client,在吞吐低的时候,要通过EpollNotifier避免epoll_wait最长时长为timeout的卡顿;但吞吐的高低是有统计周期的,例如从高变低的过程中,EpollNotifier不能及时被触发,时长为timeout的卡顿还是会发生,所以timeout越小越好。
active_socket_func_
EpollNotifier
epoll_wait
timeout
Sorry, something went wrong.
No branches or pull requests
如题,不应该通过计算定期或者超时事件最小触发时间而动态进行设置吗?
无就绪事件而有定时器来时,4ms会有延迟处理;
无就绪事件也无定时器来时,4MS触发的往下执行没有必要。
The text was updated successfully, but these errors were encountered: