Optimize complex sql #651
Merged
Optimize complex sql #651
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use a modified Version of the graph-data query statement. Instead of looping through by ourselves we use the PostgreSQL recursive WITH Query to let the database do this for us This increases the initial cost of the query but it scales much more nicely when performing queries on much more complex data or with a much bigger depth.
Although this might not be as useful, since the calculated cost of functions is not such a useful indicator for their cpu-cost.
|
Just out of interest: Of big was the performance difference of the statements? |
|
If i remember correctly somewhat along the lines of 5 times faster. But i couldn't test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Move SQL-Query logic for recursive Graph-Data queries into a PSQL-Function.