Quite strange, GQL server source code is literally just walking by fields and resolving promises, very simple and straightforward. We had something like this i

Quite strange, GQL server source code is literally just walking by fields and resolving promises, very simple and straightforward. We had something like this in our backend, but this long times is usually meant that something wastes event loop and just blocks everything from execution. It could be anything for example it could be async hooks that makes ~1000 times slower if you are using a lot of promises (since resolving fields often are just promises) since overhead is per promise. In general in latest nodejs you can do huge amount of promises and they have little to no overhead, but, again - something wrong with nodejs setup, some library populate event loop or something deeper in nodejs internals. It is not an issue with gql itself since if you have gql performance issues that means that your server is super slow in processing like anything. Our team was shocked by performance and it turns out that NodeJS is super fast and it is some libraries (like sequelize) that kills the performance, but gql is not one of them.