adaiboy edited a comment on issue #183: support Cumulative ack URL: https://github.com/apache/pulsar-client-go/issues/183#issuecomment-585606987 > The cumulative ack was left out on purpose and the reasoning was (in weighted order): > > * Keep things simple in API > * Keep things simple in client impl > * Cumulative ack doesn't provide much more performance/effciency > * Sequential individual acking will be equivalent i have doubts with the " doesn't provide much more peformance" than individual ack - Cumulative ack doesn't provide much more performance/effciency - Sequential individual acking will be equivalent i set up a test cluster, with a persistent topic , just one subscription with exclusive type, though some config in broker not be perfect, but i tuned the configure some days according to the source code and i make a test with the test cluster <img width="396" alt="截屏2020-02-1316 09 59" src="https://user-images.githubusercontent.com/3397286/74414209-ea798d80-4e7b-11ea-83a9-c1ccaa9432d8.png"> first, i modified the consumer-series add AckCumulative to compare cumulative ack with individual ack and make a producer send msg with best effort then, use cumulative consumer to consume entry , and cumulative ack when 10000 entries received, the consumer can catch the producer lastly, clear all. restart the producer, but start a consumer with individual ack just in the red frame, the consumer is much slower than producer - the produce speed is the green line - the consume speed is the yellow line as every ack is a "rpc" with CommandAck, the reduce the ack cnt will be usefull in theory.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
