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

add optimizer comments #3910

Merged
merged 33 commits into from
Mar 15, 2022
Merged

add optimizer comments #3910

merged 33 commits into from
Mar 15, 2022

Conversation

czpmango
Copy link
Contributor

@czpmango czpmango commented Feb 17, 2022

What type of PR is this?

  • bug
  • feature
  • enhancement

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:

@Sophie-Xie Sophie-Xie mentioned this pull request Feb 17, 2022
10 tasks
* 1. reduce the copy of memory between nodes
* 2. reduces expression overhead in some cases(similar to column pruning)
*/
/*
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe we should use //

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Any reference?
Google style?

Copy link
Contributor

Choose a reason for hiding this comment

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

Google style doesn't declare that the comments should use //, but it suggests that the comments style should be unified. I think it makes sense. And the most open source projects i had ever seen use the //. For now i have seen much styles in our project, it's too ugly.

// 

/*

*/

/**
 *
 */

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ACK.

yixinglu
yixinglu previously approved these changes Mar 2, 2022
bool changed_{true};
graph::QueryContext *qctx_{nullptr};
// Memo memory management in the Optimizer phase
Copy link
Contributor

Choose a reason for hiding this comment

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

What is memo?

src/graph/optimizer/OptContext.h Show resolved Hide resolved
Comment on lines +39 to +51
// +--------+--------+
// | Limit |
// | (limit=3) |
// +--------+--------+
// |
// +---------+---------+
// | AppendVertices |
// +---------+---------+
// |
// +---------+---------+
// | ScanVertices |
// | (limit=3) |
// +---------+---------+
Copy link
Contributor

Choose a reason for hiding this comment

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

Will there still be a limit node after optimization?

bool changed_{true};
graph::QueryContext *qctx_{nullptr};
// Memo memory management in the Optimizer phase
Copy link
Contributor

Choose a reason for hiding this comment

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

What's this?

@Sophie-Xie Sophie-Xie added the ready-for-testing PR: ready for the CI test label Mar 15, 2022
@Sophie-Xie Sophie-Xie merged commit 9a401f7 into vesoft-inc:master Mar 15, 2022
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.

7 participants