You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/08/07 07:00:42 UTC

[GitHub] [skywalking] wu-sheng commented on issue #3224: OAP server's performance issue

wu-sheng commented on issue #3224: OAP server's performance issue
URL: https://github.com/apache/skywalking/issues/3224#issuecomment-518967907
 
 
   For your queue question, I don't it is multiple threads visible issue. You are using 6.0.0-GA, back to there, OAP created several threads(including queue) to deal with one kind of metrics, such as service_p99, service_p95. But actually, we don't need that much, in 6.1.0 -> 6.3.0(release soon), we have optimized the thread model very much, we have a new shared consumer thread pool to avoid the root cause, which is also the root cause of your scenario, that is too many unnecessary threads, triggering high CPU load.
   
   You could dig a little more about the master branch, to see what we are doing today. From the thread dump we get from the latest version, consumer threads are still more than necessary, but we wouldn't keep to too low to support very high payload/throughput in OAP.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services