This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
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.
Ⅰ. Describe what this PR did
This PR just realize dynamic bandwidth limit, the interpret is as below
cli add
--dynamic
which could allow you to open the dynamic bandwidth limit mode.api add
Add two apis, which used to send bandwidth limit update information from peerserver to supernode.
/api/v1/peer/{id}/peerState/{dynamicRate}
The 1.0 version api./peer/dynamicrate
The 0.3 version api.field add
DynamicRate
in structPeerState
implement scheme
host_bandwidth_listener
listen to the host bandwidth, add set the 90% of current available bandwidthas
totalLimit
,also asdynamicRate
be sent to supernodedynamicRate
andProducerLoad
to calculate the priority ofpeer
, the schedule algorithm will schedule thepeer
with higher priority first.part which haven't implement now
Ⅱ. Does this pull request fix one issue?
Fixes #1427
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
Already added.
Ⅳ. Describe how to verify it
As issue #1427
Ⅴ. Special notes for reviews
Host_bandwidth_listener haven't been completed, which will be finished in next weeks.