graphql-dotnet/server always consuming memory for IntrospectionQuery
See original GitHub issueI am using graphql-dotnet/server to host my services. I have made my schema class singleton. For every IntrospectionQuery it is increasing the memory consumption by the server. So more more and request comes in memory goes high. Is there any solution to minimize this issue. Expecting your help. I am using the following code to initialize my graphQL service and my schema class is a singleton
services.AddGraphQL(_ =>
{
_.EnableMetrics = true;
_.ExposeExceptions = true;
});
services.AddSingleton<PdsGraphQlSchema>();
and inside Configure I have used following
app.UseGraphQL<PdsGraphQlSchema>();
app.UseGraphQLPlayground(new GraphQLPlaygroundOptions
{
Path = "/ui/playground"
});
Expecting your help.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Hasura consuming massive amounts of memory #4077
RAM remains high, eventually dropping to 3GB after 10-15 minutes of no usage. Postgres remains at a steady 1.5GB throughout. Is this normal?...
Read more >Justification for HotChocolate as opposed to GraphQl.Net
Performance, Hot Chocolate is now much faster that GraphQL-DotNet and uses a fraction of the memory GraphQL-DotNet uses. Read here.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I tried with
3.5.0-alpha0046
. Ran theui/playground
for 20 mins continuously polling on my graph with 30+ custom types.Memory stayed constant at 443 MB.
Closing this as solved.