Unbatch GraphQL queries
What does this MR do and why?
This MR introduces a feature flag for unbatching GraphQL queries. We plan to roll out this FF incrementally to learn the potential performance implication of unbatched queries.
It looks like unbatching made MR revert and cherry-pick specs flakier than they were so I am stubbing FF as disabled there. The actual functionality is not affected and tests pass around 40% of times on retry.
Screenshots or screen recordings
No visual changes
How to set up and validate locally
- Open any page that contains a good number of GraphQL queries (issue page is a good example)
- Check the number of
graphql
calls in theNetwork
tab of devtools - Enable unbatching feature flag
Feature.enable(:unbatch_graphql_queries)
- Refresh the page
- You should have much more graphql calls and every request should contain exactly one operation
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Natalia Tepluhina