Report a Dgraph Bug
Dgraph eats through 4gb of memory. I’m kind of on a shoestring budget here, how can I avoid this?
What version of Dgraph are you using?
Dgraph Version
$ dgraph version
Dgraph version : v21.12.0
Dgraph codename : zion
Dgraph SHA-256 : 078c75df9fa1057447c8c8afc10ea57cb0a29dfb22f9e61d8c334882b4b4eb37
Commit SHA-1 : d62ed5f15
Commit timestamp : 2021-12-02 21:20:09 +0530
Branch : HEAD
Go version : go1.17.3
jemalloc enabled : true
For Dgraph official documentation, visit https://dgraph.io/docs.
For discussions about Dgraph , visit http://discuss.dgraph.io.
For fully-managed Dgraph Cloud , visit https://dgraph.io/cloud.
Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2021 Dgraph Labs, Inc.
Have you tried reproducing the issue with the latest release?
Currently experiencing this on the latest release
What is the hardware spec (RAM, OS)?
OS: Debian 10 buster
Kernel: x86_64 Linux 4.19.0-18-amd64
Uptime: 6h 17m
Packages: 900
Shell: zsh 5.7.1
CPU: AMD EPYC 7501 32-Core @ 2x 2GHz
GPU: bochsdrmfb
RAM: 3528MiB / 3946MiB
Steps to reproduce the issue (command/config used to run Dgraph).
No specific steps, just try to stuff 10gb of data into dgraph where the dataset has 1 bi-directional relation between the node types.
Expected behaviour and actual result.
skipped
Crash logs
crash (100.5 KB)