You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/07/01 10:00:46 UTC

[GitHub] [pulsar] codelipenghui commented on pull request #7406: Improved in max-pending-bytes mechanism for broker

codelipenghui commented on pull request #7406:
URL: https://github.com/apache/pulsar/pull/7406#issuecomment-652322280


   > Regarding the lower limit per each IO thread, in which 1 single connection cannot use the entire memory space, I don't think it's an issue at all.
   
   There are some users who use few producers to publish messages, in order to have a better batch effect to improve throughput. We cannot assume 1 single connection cannot use the entire memory space. Our purpose is to control memory and make effective use of memory. I think split memory according to io thread may decrease the memory utilization.
   
   How about using a LongAdder to record the current pending bytes and remove the check tasks.


----------------------------------------------------------------
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