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 2022/06/02 15:43:31 UTC

[GitHub] [pulsar] merlimat commented on pull request #15748: [Cli tools] Disable Pulsar client memory limit by default

merlimat commented on PR #15748:
URL: https://github.com/apache/pulsar/pull/15748#issuecomment-1145013379

   > There's a regression with the tools since the memory limit cannot be adjusted
   
   @lhotari Can you elaborate on what kind of regression it was seen there? I have in general experienced the opposite, going from msg-count based to memory based.
   
   I think this change goes in the wrong direction as it completely removes the memory limit and it will easily cause OOM in the client, since there's no limitation on the producer queue size.
   
   I believe a better change here is to make the memory limit configurable for the perf producer.
   
   


-- 
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: commits-unsubscribe@pulsar.apache.org

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