GitHub / graphql-python/graphql-core issues and pull requests
Labelled with: investigate
#190 - Significant performance hit when using async resolvers
Issue -
State: open - Opened by kevinvalk almost 3 years ago
- 14 comments
Labels: optimization, investigate
#166 - Proposal: replace asyncio with anyio
Issue -
State: open - Opened by valgarf over 3 years ago
- 5 comments
Labels: help wanted, discussion, investigate
#148 - Support/help with promise-based resolvers
Issue -
State: open - Opened by AlexCLeduc about 4 years ago
- 14 comments
Labels: help wanted, discussion, feature, investigate
#143 - Test and document use of GraphQL-core with uvloop
Issue -
State: open - Opened by Cito about 4 years ago
Labels: documentation, optimization, investigate
#142 - Improve performance of async execution
Issue -
State: open - Opened by Cito about 4 years ago
- 6 comments
Labels: help wanted, optimization, investigate
#116 - Performance of validate, in the context of graphql(_sync)
Issue -
State: closed - Opened by alexchamberlain about 5 years ago
- 5 comments
Labels: investigate
#112 - Cannot unpickle DocumentNode
Issue -
State: closed - Opened by corydolphin about 5 years ago
- 6 comments
Labels: help wanted, discussion, investigate
#107 - Adding an extension field to the ExecutionResult
Issue -
State: closed - Opened by Cito about 5 years ago
- 5 comments
Labels: discussion, investigate
#101 - Slow introspection query execution for large schemas
Issue -
State: open - Opened by lonerz over 5 years ago
- 6 comments
Labels: help wanted, optimization, investigate
#100 - Issues using a deep-copied GraphQLSchema
Issue -
State: closed - Opened by pmantica1 over 5 years ago
- 3 comments
Labels: investigate
#73 - Error when trying to serialize a Python enum
Issue -
State: closed - Opened by akdor1154 almost 6 years ago
- 6 comments
Labels: investigate
#71 - Dataloader in multi-threaded environments
Issue -
State: open - Opened by jnak almost 6 years ago
- 10 comments
Labels: help wanted, discussion, investigate