[Fixed]-Graphene-python performance issues for large data sets


Try using a better profiler like Silky, it will show you a breakdown based on queries Django fires to the DB, as well as a neat cProfiler overview. I would suspect an issue in extraneous DB calls. Graphene tends to make Django do a lot of per-field calls while constructing the response and they might not be showing up in the debugger response.

Without more information on the setup – models, resolvers and graphql queries – it’s very hard to judge.

Leave a comment