[ 
https://issues.apache.org/jira/browse/ROCKETMQ-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136464#comment-16136464
 ] 

ASF GitHub Bot commented on ROCKETMQ-253:
-----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/140
  
    
    [![Coverage 
Status](https://coveralls.io/builds/12933324/badge)](https://coveralls.io/builds/12933324)
    
    Coverage decreased (-1.9%) to 37.329% when pulling 
**9f3af40fd1396048ef2248ee7c015a41c4b7b7b3 on lizhanhui:compress_heartbeat** 
into **33a99a4148cd216c800276029003f0ea6db14045 on apache:develop**.



> Compress RegisterBrokerBody
> ---------------------------
>
>                 Key: ROCKETMQ-253
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-253
>             Project: Apache RocketMQ
>          Issue Type: Improvement
>          Components: rocketmq-broker, rocketmq-commons, rocketmq-namesrv
>            Reporter: Zhanhui Li
>            Assignee: yukon
>
> RocketMQ Brokers periodically register itself against namesrv to maintain its 
> liveness.
> In case a broker has many topics, a 10 thousand or more, two major 
> problematic issues show up:
> 1) Current serialization of RegisterBrokerBody would create a large String 
> object, which stresses GC  a lot, especially when G1 is used.
> 2) Transmission this bulk of data takes up significant portion of bandwidth.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to