Skip to content
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

High memory and CPU usage with a noop graphql-middleware #417

Open
amitgud-doordash opened this issue Jul 9, 2021 · 1 comment
Open

Comments

@amitgud-doordash
Copy link

We are experiencing very high memory usage when we add even a noop middleware to our express Apollo GraphQL application. Do we have an idea of what memory / CPU overhead we should expect with the graphql-middleware? Using the latest version (6.0.10).

Screen Shot 2021-07-09 at 10 38 10 AM

@amitgud-doordash
Copy link
Author

Just add some more color to this issue. The schema in the application is big, however the middleware itself is not going anything interesting.

+const noopMiddleware = async (
+  resolve: any,
+  root: any,
+  args: any,
+  context: Context,
+  info: any
+) => {
+  return await resolve(root, args, context, info)
+}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant