Hi @the-alchemist,
Wondering if this issue is still current, it would be nice if you can re-do your test using our latest dgraph docker image, as since Jul '19 we have done important improvements to the product.
Something that you can collect while testing are cpu profiles and memory profiles.
Also, you can try reproducing the test using Slash GraphQL our managed GraphQL service.
If the issue is still happening, we will be more than happy to investigate.
Best,
Omar