Closed
Conversation
Author
|
猜测作者可能是想让weightInvokers作为队列不断存储要调用的invoker, |
Author
|
orz,终于好了,之前手滑挪了文件夹位置…… |
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修正weightSequence过快增长导致的高权重机器调用过多问题。
currentWeight本应为每轮加一,但原错写为每次调用加一。
设有两台机器权重分别为1和2,设计应为第一轮分别执行一次,第二轮在第二台执行一次。
但原算法为第一轮各有1/2的机会执行一次,第二轮在第二台执行一次。
造成高权重机器被调用次数过多。
修正为每次检查sequence完成一轮后才增加currentWeight。