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
Adding a rollback() at the beginning of every request adds a large overhead of about 30s for retrieving only 4000~ vertices with indices enabled. Removing rollback() speeds up all requests to be in the range of milliseconds. However, removing rollback() causes inconsistencies with deleting edges.
We follow https://docs.janusgraph.org/latest/tx.html pretty closely for adding and updating vertices and edges and haven't encountered inconsistency issues without rollback().
Are there no way to refresh the graph cache when deleting objects? Can there be more docs regarding this issue?
The text was updated successfully, but these errors were encountered:
In reference of http://tinkerpop.apache.org/docs/current/reference/#transactions and #500.
Adding a
rollback()
at the beginning of every request adds a large overhead of about 30s for retrieving only 4000~ vertices with indices enabled. Removingrollback()
speeds up all requests to be in the range of milliseconds. However, removingrollback()
causes inconsistencies with deleting edges.We follow https://docs.janusgraph.org/latest/tx.html pretty closely for adding and updating vertices and edges and haven't encountered inconsistency issues without
rollback()
.Are there no way to refresh the graph cache when deleting objects? Can there be more docs regarding this issue?
The text was updated successfully, but these errors were encountered: