By "improve message throughput performance" are you talking about *overall* message throughput or throughput for a few selected consumers?
Generally speaking, reducing consumerWindowSize will help when messages are accumulating on one consumer and other consumers have none (i.e. consumer starvation). This typically happens when you have a consumer that is slower than the others. The speed of the network between the consumer and the broker isn't as much of an issue as the speed at which the consumer is processing the messages. Justin On Fri, Mar 18, 2022 at 4:56 PM Steigerwald, Aaron <asteigerw...@brandesassociates.com.invalid> wrote: > Hello, > > Does it make sense that setting consumerWindowSize=0 on the client's > connection URL in order to disable client message buffering would improve > message throughput performance given the following scenario: > > Artemis version: 2.3.0 > Number of queue consumers: 8 from 8 different systems, some of which are > geographically separated from the broker but have low latency network > connections. > Message type: byte > Average message size: less than 10 kilobytes > > Thank you, > Aaron Steigerwald >
