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 understand that graphene can execute resolvers in parallel using a thread pool per #314
What I'm asking is a little different: I want distinct queries to each run their resolvers synchronously, but I want several queries to run at the same time using an executor pool. If these queries are sharing the same Schema instance will this lead to problems?
If this isn't possible, I can make a workaround just by making instantiating multiple Schemas and pooling them, I just check that this is actually necessary before going through the effort.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I understand that graphene can execute resolvers in parallel using a thread pool per #314
What I'm asking is a little different: I want distinct queries to each run their resolvers synchronously, but I want several queries to run at the same time using an executor pool. If these queries are sharing the same
Schema
instance will this lead to problems?If this isn't possible, I can make a workaround just by making instantiating multiple
Schema
s and pooling them, I just check that this is actually necessary before going through the effort.The text was updated successfully, but these errors were encountered: