You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing feature request and this feature request is not already filed.
I believe this is a legitimate feature request, not just a question or bug.
Feature Request Description
Preliminary testing shows that the speed bottleneck is at the merge node stage. Is it possible to optimize this by changing to a concurrent merge?
Can I remove the “await” and use “create_task” and “gather” in the following code? Was the use of await here because some graph databases, like NetworkX, do not support concurrent node insertion, so everything was changed to a serial mode?
The text was updated successfully, but these errors were encountered:
Too many concurrent requests can generate excessive database connections, consuming a large amount of resources and leading to a performance decline. The correct approach is to use batch mode for data queries. The main branch has already been optimized following this principle. Currently, the performance of PostgreSQL and Neo4j has been significantly improved.
Do you need to file a feature request?
Feature Request Description
Preliminary testing shows that the speed bottleneck is at the merge node stage. Is it possible to optimize this by changing to a concurrent merge?
Can I remove the “await” and use “create_task” and “gather” in the following code? Was the use of await here because some graph databases, like NetworkX, do not support concurrent node insertion, so everything was changed to a serial mode?
The text was updated successfully, but these errors were encountered: