That would be the very point that I corrected myself on earlier, where I had somehow misread the second question numbered 2 originally. Per the correction, the same answer to the first question 2 applied there also, which was "This is the same as the default. Persistent messages will be sent synchronously, except inside a transaction. Non-persistent messages will be sent asynchronously." Governing those cases is the reason the forceSyncSend option exists.
Robbie On Tue, 11 Jun 2019 at 17:23, akabhishek1 <mailbox.abhishek.ku...@gmail.com> wrote: > > Hi Robbie, > > Based on your input, i did some testing and got different test result in > terms of TPS(transaction per second) for below conditions > > 1. jms.forceSyncSend=true + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, > DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1200. > > 2. NO Setting @Connection Level + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, > DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1800. > > > As both conditions tend to SYNCHRONOUS. I wondered to see different test > result with variance of 600TPS. My sourceCode is completely same for both > conditions except setting at connection level. > > Expectation - As both conditions tend to SYNCHRONOUS, so i am expecting > approx. same TPS for both conditions. > > Could you please provide some insights, why i am getting different Test > throughput as both are synchronous? Am i missing something? > > Client - qpid-jms-client-0.43.0 > Java8 > Broker - Azure ServiceBus(Premium) > > Regards, > Abhishek Kumar > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
