You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@age.apache.org by "MatheusFarias03 (via GitHub)" <gi...@apache.org> on 2023/09/15 19:20:06 UTC
[GitHub] [age] MatheusFarias03 commented on issue #1087: AGE python driver works slowly on large data
MatheusFarias03 commented on issue #1087:
URL: https://github.com/apache/age/issues/1087#issuecomment-1721734495
> But getting all nodes and edges takes 9m+
It might be associated with the way you get the edges (the query you provided does not show the retrieval of the edges, but I assume you are trying to return them in some way). If it is something like the query below, it may take more time than usual.
```sql
SELECT * from cypher('graph', $$
MATCH (V)-[R]-(V2)
RETURN V,R,V2
$$) as (V agtype, R agtype, V2 agtype);
```
This is discussed in issue #628.
As answered there by John:
> The regular MATCH uses nested JOINS to find the results whereas the VLE MATCH uses a graph pathing function. It is a different engine that is finding the matches in each case. The problem with the regular MATCH is that these JOINS can nest way to deep, depending on the graph. This is compounded by the labels being in separate tables.
So, maybe the query below may run faster with python:
```sql
SELECT * from cypher('graph', $$
MATCH (V)-[R]->(V2)
RETURN V,R,V2
$$) as (V agtype, R agtype, V2 agtype);
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org