Does query variables have extra overhead or will those queries have the same performance? { q(func: ...) @filter(...) { ... } } { matching as var(func: ...) qFunc as var(func: uid(matching)) @filter(...) q(func: uid(qFunc)) { ... } } As you know I am working on a querybuilder …

Does query variables have extra overhead?

anand (Anand Chandrashekar) August 8, 2020, 1:17pm 2

Per this doc, a) query blocks are executed in parallel, and b) you cannot have a defined but unused variable. With those constraints, AFAIK, your approach is good.

1 Like

Topic		Replies	Views
Optimize query variables based on requested data Dgraph kind:enhancement , kind:feature , area:querylang , area:querylang:vars	3	687	August 10, 2020
Two equivalent queries, one is slow and the other one is fast Dgraph	3	828	January 6, 2020
Directive idea to support var blocks in GraphQL GraphQL kind:feature , area:querylang:vars , custom-directive	7	983	June 5, 2024
[DGraph Cluster] 600ms vs 6s: Query response times differ greatly based on the shard that is executing it Dgraph dgraph , kind:bug	4	634	August 29, 2022
How the query works when meets functions？ Dgraph	3	410	November 7, 2019

Does query variables have extra overhead?

Related topics