wu-sheng opened a new issue, #12416:
URL: https://github.com/apache/skywalking/issues/12416

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar feature requirement.
   
   
   ### 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.
   
   <img width="1126" alt="image" 
src="https://github.com/apache/skywalking/assets/5441976/2a9daa95-311e-4c58-a0d3-3ecb3f18d1ce";>
   <img width="723" alt="image" 
src="https://github.com/apache/skywalking/assets/5441976/45224246-b7f1-4071-ab5e-173599e3fa85";>
   
   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?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to