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.
The throughput problem reappeared because of this commit 1ea53e9
test case: #213
Although in actual production there will be no sub-substreams above 100 levels, this is indeed a problem. After regression testing, the current code will show a significant throughput drop when it is around 800.
perf
./target/release/examples/throughput_test 800
master branch: CPU consumption of
distribute_to_substream
function accounts for more than 50%patch branch: CPU consumption problem of
distribute_to_substream
function cannot be clearly observed, about 2.5%This is a classic continuous memory and segmented memory overhead problem. In a test scenario under full pressure, such memory issues will be triggered frequently and cause huge overhead.