11 replies

Query optimisation

Hey, I'm optimising some queries, and found that these 2 seemingly identical queries behave very differently in term of performance

g.V().
  union(
    has("account", "id", "my_account"),
    has("account", "id", "my_account").
    out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  union(
    has("account", "id", "my_account"),
    has("account", "id", "my_account").
    out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  has("account", "id", "my_account").
  union(identity(), out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  has("account", "id", "my_account").
  union(identity(), out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

The 2nd query performed about 10 times faster than the first. Can anyone with experience let me know what's the different for the 2? And what I should watch out for to avoid bad performing query like the first one? Thank you.

Solution

If would suggest looking at the profile of the query and post it here as well as what database you are using (e.g. Gremlin Server, JanusGraph, Neptune, etc.) to see where the time is being spent. Without having more information it is difficult to give specifics as to why they query is slow.

Without any additional context I would take a guess that most of the difference in time is being spent doing

has("account", "id", "my_account")

has("account", "id", "my_account")

since the first version is doing that filter twice.

Jump to solution

Apache TinkerPop•2y ago•

11 replies

Painguin

Query optimisation

Hey, I'm optimising some queries, and found that these 2 seemingly identical queries behave very differently in term of performance

g.V().
  union(
    has("account", "id", "my_account"),
    has("account", "id", "my_account").
    out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  union(
    has("account", "id", "my_account"),
    has("account", "id", "my_account").
    out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  has("account", "id", "my_account").
  union(identity(), out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

g.V().
  has("account", "id", "my_account").
  union(identity(), out("owns")).
  union(
    out("completed").values("points"),
    inE("rewarded").has("claimed", true).values("points")).
  sum().
  next()

Solution

has("account", "id", "my_account")

has("account", "id", "my_account")

since the first version is doing that filter twice.

Jump to solution

Query optimisation

Similar Threads

Query optimisation

Similar Threads

Similar Threads

Similar Threads