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
When you have a database with a moderate amount of data (say, 3000 relations) , the query match $x sub relation; takes 11 seconds to execute on localhost, and significantly longer in a database hosted on a remote server.
This is because each relation concept loaded triggers a serial Concept API call to getPlayersByRoleType. With 20ms network latency, this query would take over a minute - to load just 3000 relations.
NOTE: This issue also affects schema queries, which do serial Concept API calls to getSupertype for each Type loaded.
Proposed Solution
This issue could be solved by introducing an Async Concept API, or by not loading the connected concepts, or by an alternative solution such as adding options to load connected vertices with the query (discussed in the Async Concept API feature proposal)
The text was updated successfully, but these errors were encountered:
Problem to Solve
When you have a database with a moderate amount of data (say, 3000 relations) , the query
match $x sub relation;
takes 11 seconds to execute on localhost, and significantly longer in a database hosted on a remote server.This is because each relation concept loaded triggers a serial Concept API call to
getPlayersByRoleType
. With 20ms network latency, this query would take over a minute - to load just 3000 relations.NOTE: This issue also affects schema queries, which do serial Concept API calls to
getSupertype
for each Type loaded.Proposed Solution
This issue could be solved by introducing an Async Concept API, or by not loading the connected concepts, or by an alternative solution such as adding options to load connected vertices with the query (discussed in the Async Concept API feature proposal)
The text was updated successfully, but these errors were encountered: