-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance issues related to complete_value on large datasets #189
Comments
JCatrielLopez
changed the title
Performance issues with complete_value on large datasets
Performance issues related to complete_value on large datasets
Jan 11, 2023
Possibly related to this graphql-js issue |
Thanks for reporting. Will look into this when I have more time, probably only after releasing 3.3. It would be helpful if you could post example code with dummy data to reproduce this. |
schema.graphql:
server.py:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! We've noticed that returning a list of 5k elements, with a couple of nested objects is pretty slow:
By itself it's not really a slow function, but its executed 30k times. Is there any way to reduce the overhead by reducing the number of times this function is invoked?
Tested on Python 3.8 and graphql-core==3.2.3
The text was updated successfully, but these errors were encountered: