If you can give more memory to Dgraph, that always helps for sure. I’d keep the batch sizes reasonable, like say 1000 edges per transaction. You could run the txns concurrently, say 10 txns in-flight at any point of time.
If you can get a heap profile when Dgraph is going to go OOM, that’d help determine what is the cause.