You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that we could implement a small but effective enhancement to batching.
It may happen that even if you enable batching you come to create entries with 1 only message.
Processing batch messages requires a good amount of resources, both on the broker and on the client side.
Especially when you are using PIP-105, Broker side filtering, you have to unpack (and decompress) the whole entry in order to process the very single message.
So my proposal is to change the (Java) producer, to make it produce a regular message instead of a batch message if the batch contains only 1 message.
Testing should cover:
regular batch sending using the Java producer
KEY based batcher builder
The text was updated successfully, but these errors were encountered:
I think that we could implement a small but effective enhancement to batching.
It may happen that even if you enable batching you come to create entries with 1 only message.
Processing batch messages requires a good amount of resources, both on the broker and on the client side.
Especially when you are using PIP-105, Broker side filtering, you have to unpack (and decompress) the whole entry in order to process the very single message.
So my proposal is to change the (Java) producer, to make it produce a regular message instead of a batch message if the batch contains only 1 message.
Testing should cover:
The text was updated successfully, but these errors were encountered: