You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have made few load tests using same logic with and without fields with FieldResolver
query with FieldResolver has 2x worse performance than without them
field resolvers I used are very simple ones
Depending on the scale a few more fields could result in a lot more function calls in the resolvers. That coupled with Node.js / JS single threaded nature might be problematic.
My apologies, but I am not seeing the exact lines in the numbers above where the 2x worse performance is demonstrated. That certainly does seem excessive. I am not sure if it is something that we can help with, but if you are able to set up a minimal reproduction using just vanilla graphql JS, that might help.
I have made few load tests using same logic with and without fields with FieldResolver
query with FieldResolver has 2x worse performance than without them
field resolvers I used are very simple ones
Any ideas why? How to improve?
query without field resolvers
query with field resolvers
results with field resolvers (4 of them)
results without field resolvers
The text was updated successfully, but these errors were encountered: