-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
zh-CN:Trans for 'Clarify when nextTickQueue is processed' #2026
New issue
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
直译 饿死
不够生动形象。。。 递归更像撑死。
直接说 阻塞I/O
会不会好一些
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I/O调用因为异步轮询不断调用process.nextTick()始终得不到调用,所以始终处于“饥饿”状态,这是对的。而是说时间轮询队列被撑死了。
我们等一下其它人看法吧,我通读此文感觉这里的确是“饿死”,是说顺序执行的I/O始终得不到机会执行。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
原文:
This can create some bad situations because it allows you to "starve" your I/O by making recursive process.nextTick() calls, which prevents the event loop from reaching the poll phase.
IMHO, 我是觉得没什么太大问题 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
如果没理解错的话,event loop
应该翻译成 事件循环
吧。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Ref:#1804
@nodejs/nodejs-cn