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

Improve the traverse executor performance #5308

Merged
merged 3 commits into from
Feb 6, 2023

Conversation

yixinglu
Copy link
Contributor

@yixinglu yixinglu commented Feb 3, 2023

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

How do you solve it?

tuning the one step expand in traverse executor

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 force-pushed the iterator-improve branch 2 times, most recently from 9885c2a to 5ec3466 Compare February 6, 2023 01:29
@yixinglu yixinglu marked this pull request as ready for review February 6, 2023 01:32
@yixinglu yixinglu added the ready-for-testing PR: ready for the CI test label Feb 6, 2023
Copy link
Contributor

@jievince jievince left a comment

Choose a reason for hiding this comment

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

LGTM

@yixinglu yixinglu merged commit be325e5 into vesoft-inc:master Feb 6, 2023
@yixinglu yixinglu deleted the iterator-improve branch February 6, 2023 06:01
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