-
Notifications
You must be signed in to change notification settings - Fork 409
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
Can we improve query performance? #1902
Comments
This issue is stale because it has been open 60 days with no activity. Remove "Abondoned" label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for further 14 days with no activity. |
@sanket-uptycs We are looking into performance improvements in general. I will point out that the below query is a bit redundant by using MERGE and SET. MERGE is basically MATCH X and if X doesn't exist CREATE X. Since you have already MATCHed them, you don't need to do it again. Additionally, since you are creating a new edge, you don't need to SET it.
I believe this is equivalent, and likely faster -
|
This issue is stale because it has been open 60 days with no activity. Remove "Abondoned" label or comment or this will be closed in 14 days. |
I am trying following query. Can we improve query performance?
I have gin index on node1 node2 and ATTACHED_TO edge.
But it is taking
Planning Time: 0.309 ms Execution Time: 44548.615 ms
Here is the query plan.
select count(*) from graphdb._ag_label_edge;
| 324030 |
select count(*) from graphdb._ag_label_vertex;
| 220385 |
Number of Node and Edge types : 50+
The text was updated successfully, but these errors were encountered: