Description

As we know, the performance optimization is a long-term challenge that needs to be done consistenly, and we hope DS is more stable and high performance.
So this is a parent issue to track and summarize the optimization issue for ds 2.0 performance.
If you have some performance test and suggestion for ds, welcome to comment it.
if you are interested in performance optimization, welcome to do it together.

Functional

• Master
  • [DS-6694][Master] Reduce the refresh resource interval of LowerWeight #6695
  • [Improvement][MasterServer] improve master scan and handle commands #6849
  • [Feature][MasterServer] reduce db query operation when process instance running #6891
  • [Feature][MasterServer] Add cache manager for Master #6963
• Worker
  • [Bug] [Worker] Worker fakes death when it stop itself fail. #6616
  • [Improvement][Log] optimize task log path to reduce task running time #6665
  • Why worker take more time to handle task when it's busy? #6675
• Zookeeper
  • [Improvement][Server] Change the registry session timeout #6660
• DB
  • [Bug] [MasterServer] With MySQL 8.0, Druid make thread blocked to wait lock when load class  #6483
• Netty
  • [Bug] [Server] Netty client create too many channel and make busy network #6653
• Performance Test
  • Stability Test for DS #6678