Search before asking
Description
Within these months, @hanahmily and I took a lot of time to improve BanyanDB + OAP performance, and made a good progress.
Meanwhile, we noticed the UI widgets applied a lot of queries(over dozens of times) separately, which reached the browser limitation(less than 6 concurrently). So, many queries have to pend on the previous responses.
We should consider merging queries by leveraging GraphQL capabilities.
We could allow the codes to control the merging through a code level configuration, and set the default one as 6, which means, (max)6 widget queries could be merged into one GraphQL query.
Use case
@wankai123 We should observe the performance and GraphQL service engine performance behavior after this is done by UI.
Ideally, we should see the query has been run concurrently driven by GraphQL handler, then have a larger trace to cover multiple queries.
This may need to move the start point of the query span creation a little forward.
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct
Search before asking
Description
Within these months, @hanahmily and I took a lot of time to improve BanyanDB + OAP performance, and made a good progress.
Meanwhile, we noticed the UI widgets applied a lot of queries(over dozens of times) separately, which reached the browser limitation(less than 6 concurrently). So, many queries have to pend on the previous responses.
We should consider merging queries by leveraging GraphQL capabilities.
We could allow the codes to control the merging through a code level configuration, and set the default one as 6, which means, (max)6 widget queries could be merged into one GraphQL query.
Use case
@wankai123 We should observe the performance and GraphQL service engine performance behavior after this is done by UI.
Ideally, we should see the query has been run concurrently driven by GraphQL handler, then have a larger trace to cover multiple queries.
This may need to move the start point of the query span creation a little forward.
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct