Still have questions? Reach out to our team directly and we'll be sure to help you out.
We’ve chosen a log based scale between TouchedNodes and QueryCost to help make your planning easier. We don’t really want you worry about the difference between touching 2400 nodes and 2600 nodes, but if a query is 10x more complex, we’ll charge you an extra credit.
Astute readers will notice that firing a single query that touches 500 nodes will be cheaper than firing 5 queries that each read 100 nodes, thus multiple query blocks into a single /graphql request is a great way to reduce the number of credits your app consumes.
Dgraph stores each record as a set of nodes, so if you return 5 records with 10 fields each, then you will have touched 50 nodes. Additionally, if you’ve searched for these records, then we’ll have touched a few index nodes (depending on how the index is set up), so maybe you’ve touched 65 nodes for this query.
See how Dgraph compares to other databases such as Neo4j, TigerGraph, and more.
FIND THE ONE THAT’S RIGHT FOR YOUSEE COMPARISON