Skip to content
Discussion options

You must be logged in to vote

In several protocols RabbitMQ supports you can ack multiple deliveries at once. And no, it is not "too slow to ack individually". What is slow is when you do not allow RabbitMQ to deliver more than one message before the previous one is acked, that is, when the prefetch values of the consumer channel is set to 1 and not something like 256. Besides other things like the replication factor of the queues, whether the publisher uses confirms and using what approach, and so on.

There is an operation to purge the queue, that is, delete all messages in Ready state in it.

Streams allow you do acknowledge N messages at once.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by michaelklishin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #6306 on November 02, 2022 05:32.