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
Inaccurate tracing request times #4754
Comments
Restarting seemed to fix the issue. I can't reproduce this. Leaving it open in case anyone has any ideas? |
having the same issue. The request time is increasing over time. only when I restart the server or redeploy its "fast" for a while and gets slower over time. |
Can agree with @dude-awesome, the application was open for two hours to get the above figures. It's reproducible if you keep it up for a long time. |
its also slowing down my general apollo-server performance. so the queries are really getting slower over time. only a redeploy will fix this for some hours. CPU and Memory is fine. so there are no critical peaks or memory leaks but my queries are very slow. |
Possibly resolved in #7000 ? Sorry we never responded to this issue. If you get the chance to upgrade to AS4 and validate the fix that would be great. If the issue persists I'd be happy to reopen this. |
Apollo Version: 2.19.0
Package: apollo-server-express
Using the GraphQL UI, I'm calculating response times to various requests. All of the "Request" / "Response" times seem to be heavily exaggerated, hundreds of times larger than they are in reality.
This query did not take ~800ms to return. Using firefox dev tools we see a much more realistic 4ms:
This happens no matter my query and setup. The "account" phase, which is the bit that actually matters, seems to be the correct time. It's just a little disconcerting seeing it say the request took so long.
The text was updated successfully, but these errors were encountered: