Skip to content
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

Front-end time-consuming Query optimization #174

Open
ahonn opened this issue Sep 19, 2024 · 0 comments · Fixed by #216
Open

Front-end time-consuming Query optimization #174

ahonn opened this issue Sep 19, 2024 · 0 comments · Fixed by #216
Assignees
Labels
enhancement New feature or request P-Medium

Comments

@ahonn
Copy link
Contributor

ahonn commented Sep 19, 2024

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:

  • a query for querying the overall data and the transaction id list
  • a query for querying the details of the transaction.

cc @Flouse @yuche @Vibes-INS

@Flouse Flouse added enhancement New feature or request P-Medium labels Sep 23, 2024
@Flouse Flouse linked a pull request Sep 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P-Medium
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants