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

Compile time optimizations #134

Merged
merged 6 commits into from
Oct 26, 2023
Merged

Compile time optimizations #134

merged 6 commits into from
Oct 26, 2023

Conversation

swilly22
Copy link
Contributor

Seperate execution plan optimisations into compile time optimizations and runtime optimizations
Compile time optimizations are cached.

Compile time optimizations:

  1. reduceScans
  2. compactFilters
  3. filterVariableLengthEdges
  4. reduceCartesianProductStreamCount
  5. applyJoin
  6. reduceTraversal
  7. reduceDistinct
  8. reduceCount

Runtime optimizations:

  1. utilizeIndices
  2. optimizeLabelScan
  3. seekByID
  4. reduceFilters
  5. applyLimit
  6. applySkip

@@ -238,6 +238,20 @@ bool OpBase_IsWriter
return op->writer;
}

// indicates if the operation is an eager operation
bool OpBase_IsEager
Copy link
Contributor

Choose a reason for hiding this comment

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

there is already one like this called ExecutionPlan_isEager

Copy link
Contributor Author

Choose a reason for hiding this comment

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

A bit confusing but ExecutionPlan_isEager checks to see if the Execution-Plan spanned from the given root contains an eager operation while OpBase_IsEager checks if the given operation is an eager op.

@swilly22 swilly22 merged commit ec02820 into master Oct 26, 2023
8 of 9 checks passed
@swilly22 swilly22 deleted the compile-time-optimizations branch October 26, 2023 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants