GraphQL requests for issue browsing & co are really slow.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I am user of a big public gitlab instance, more specifically the one hosted by the haskell foundation to host the GHC project, on https://gitlab.haskell.org.
I have noticed that certain graphql requests take a huge amount of time, more specifically, things that I need very commonly like
- opening the issues page
- opening a specific issue from this issue page
Opening the issues landing page results into a graphql request to the graphql API that tries to retrieve the first 100 issues, which, to my surprise takes over 2 seconds to process for the server.
This is surprising to me because taking 100 out of 10000 things should not take anywhere near the goal stated in the gitlab developer documentations that any graphql request should take at most 100ms but still it takes 23 times that time.
Additionally, the developer documentation talks about "caching" and if anything is cached then it should be the first 100 issues, right? Why does it still look like this is done on a cold cache? And again, even against a cold cache, this should take a fraction of the time it actually does.
I first thought that this was an issue with the gitlab instance hosted at haskell.org, but then I checked the issue tracker of this specific repo and saw even higher load times to complete that request.
Thank you for consideration of this issue.