On Wed, 19 May 2021 at 17:04, Gordon Sim <g...@redhat.com> wrote: > On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy <nami...@hpe.com> wrote: > > Is Broker - J optimized for the below mentioned scenario. > > I believe the java broker will indeed perform better for synchronous > publish. Best thing is to run a quick test though. >
Broker-J does not rely on a flush timer, instead simply combining all DB interactions that are running concurrently into a single write... So, theoretically, for this particular case you shouldn't see the same sort of latency... but as Gordon says you should really test with something that best represents your actual expected workload. In general if you care about performance then sending individual messages synchronously is not a good choice. -- Rob > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
