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
Some pages in the front-end query data are processed through a huge graphql query, which may cause the server to process the request very time-consumingly (combine different APIs and return the data after calculation).
In this case, we can optimize the request by splitting the query to reduce the time consumption and avoid request timeout.
All queries basically contain a list of transactions. When there is only one query on a page, the time consumption may increase, resulting in a Vercel Function timeout.
A better way to split this part of the query to:
a query for querying the overall data and the transaction id list
a query for querying the details of the transaction.
Some pages in the front-end query data are processed through a huge graphql query, which may cause the server to process the request very time-consumingly (combine different APIs and return the data after calculation).
In this case, we can optimize the request by splitting the query to reduce the time consumption and avoid request timeout.
Query
All queries basically contain a list of transactions. When there is only one query on a page, the time consumption may increase, resulting in a Vercel Function timeout.
A better way to split this part of the query to:
cc @Flouse @yuche @Vibes-INS
The text was updated successfully, but these errors were encountered: