[GitHub] [iotdb] ericpai commented on pull request #3797: [IOTDB-1564] Make hearbeat and election timeout parameters be configurable

[GitBox <gi...@apache.org>]

ericpai commented on pull request #3797:
URL: https://github.com/apache/iotdb/pull/3797#issuecomment-911259726


   @jixuan1989 I make a brief test with 3 nodes cluster without any read/write pressure. And use Arthas tool to analyze the CPU usage. Here is my conclusion:
   
   1. With heartbeat_interval_ms=100, the MetaHeartbeatThread and DataHeartbeatThread costs <0.1% CPU. And with heartbeat_interval_ms=1000, they costs <0.01% CPU. There's no significant impaction if we decrease the heartbeat interval.
   2. Under no outer pressure environment, with heartbeat_interval_ms=100, the headertbeatThread CPU costs about 34.09% of the whole IoTDB program cost. And with heartbeat_interval_ms=1000, the percentage is 1.27%. Because CPU cost in total is very low, the percentage difference is huge.
   
   I think the side effect of CPU is acceptable.
   
   Attachments for reference:
   1. hb-dashboard-100.png: The snapshot of dashboard of CPU of one leader node under heartbeat_interval_ms=100 
   2. hb-dashboard-1000.png: The snapshot of dashboard of CPU of one leader node under heartbeat_interval_ms=1000 
   3. 1. hb -100.svg: The flame graph of CPU of one leader node by sampling at least 10 seconds under heartbeat_interval_ms=100 
   4. 2. hb -1000.svg: The flame graph of CPU of one leader node by sampling at least 30 seconds under heartbeat_interval_ms=1000
   [CPU-performance.zip](https://github.com/apache/iotdb/files/7096637/CPU-performance.zip)
   


-- 
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: reviews-unsubscribe@iotdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org