Voon Yong Shing

Hi, doing something similar to this, we are using directed edges, and trying to create >8 million edges, and noticed this similar trend in performance, where after the approx 200k...

Hi @jrgemignani, I've created a separate issue with the sample query and what we've tried and the query plan here https://github.com/apache/age/issues/2198

> [@ysvoon](https://github.com/ysvoon) Could you provide the query plan? Also, are you increasing the size of Person? Meaning, adding in more people? > > For the query plan, use explain analyze...

> [@ysvoon](https://github.com/ysvoon) What I can say about your query above is that it is not scalable for larger datasets; let me see if I can explain why,... > > Basically,...

> This is due to the 2 MATCH commands used in creating the edges, as you are building your edges from the Person table; this is a O(n^2) operation. >...

@jrgemignani I see, thank you for the information, is there a set date for the 1.6.0 release to be pushed out? Additionally, would like to ask if others been successful...

@jrgemignani Hi, while you are checking the above comments, may I additionally ask if the 1.6.0 release will be backward compatible? For e.g.: might we need major code changes should...

@jrgemignani Hello, haven't heard back in some time, just wanted to check if everything's okay and if you've managed to have a look at the above comments? :)

@jrgemignani Hi! Just bumping the issue, any feedback or suggestion from you will be greatly appreciated!

@jrgemignani Got it, thanks! May I ask what performance issues are you referring to and if they are related to any of the issues mentioned above in this GitHub issue?