You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1566 increases the cost/complexity of the GraphQL queries. The query cost goes up ~20x due to that PR. We should fix this before the next release. 2-part solution here:
Decrease the number of associatedPullRequests to 1, since for every commit we are only interested in a single PR (the one used to submit the commit). Doing this brings back the cost to original, so ~20x savings.
Add some tests to verify the cost of our GraphQL queries. Any future issues can be caught using these tests.
I would say, we block the next release on this issue since IMO it's important to fix this.
The text was updated successfully, but these errors were encountered:
Can you explain how you compute the cost of a request? Is this something the API returns?
I don't follow why setting associatedPullRequests to 1 helps: I was under the impression that each commit to main has a single associated pull request anyway. I tried
I don't follow why setting associatedPullRequests to 1 helps: I was under the impression that each commit to main has a single associated pull request anyway.
That is correct. But if you say first: 1 vs. first: 30 (for associatedPR), the cost of the query that you get is different. I presume GitHub makes an approximate charge based on the complexity of the query, so a query for more items is more expensive even if it ends up returning lesser number of items.
#1566 increases the cost/complexity of the GraphQL queries. The query cost goes up ~20x due to that PR. We should fix this before the next release. 2-part solution here:
associatedPullRequests
to 1, since for every commit we are only interested in a single PR (the one used to submit the commit). Doing this brings back the cost to original, so ~20x savings.I would say, we block the next release on this issue since IMO it's important to fix this.
The text was updated successfully, but these errors were encountered: