Here is a screenshot from our grafana.
Can you please let me know why Dgraph is using more than 10GB of RAM to return a specific query? This is not looking normal. My database is really small and I don’t think that this is related to our data. Also, the query itself doesn’t try to expand predicates deeper in the graph.
This is a BIG blocker for us. In your previous comment, you mention that there is the option to change the badger configuration. Can you please elaborate more on that, and how I apply those changes?