Skip to content
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

Traverse executor in parallel #5314

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

yixinglu
Copy link
Contributor

@yixinglu yixinglu commented Feb 6, 2023

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

run traverse executor in parallel when the number rows of response greater than the threshold value.

How do you solve it?

Expand each response of RPC in parallel

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

  • Unit test(positive and negative cases)
  • Function test
  • Performance test
  • N/A

Affects:

  • Documentation affected (Please add the label if documentation needs to be modified.)
  • Incompatibility (If it breaks the compatibility, please describe it and add the label.)
  • If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
  • Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

@yixinglu yixinglu added the ready-for-testing PR: ready for the CI test label Feb 6, 2023
@yixinglu yixinglu force-pushed the comm-multiple-traverse-opt branch 5 times, most recently from d54970a to 5f3989b Compare February 6, 2023 12:31
@yixinglu yixinglu requested review from nevermore3, codesigner, czpmango, jievince and xtcyclist and removed request for nevermore3 February 6, 2023 12:40

folly::Future<Status> TraverseExecutor::expandOneStep(RpcResponse&& resps) {
auto numRows = numRowsOfRpcResp(resps);
if (numRows < FLAGS_traverse_parallel_threshold_rows) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

< ???

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When return too many vertices from storage, the collect task will speed a lot time. so not use the parallel execution in that case.

@yixinglu yixinglu merged commit 9e2523c into vesoft-inc:master Feb 7, 2023
@yixinglu yixinglu deleted the comm-multiple-traverse-opt branch February 7, 2023 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants