Hi Gordon,
Thanks for the info, that helps a lot. Is Broker - J optimized for
the below mentioned scenario.
Regards,
Nancy
-----Original Message-----
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Wednesday, May 19, 2021 2:10 PM
To: users@qpid.apache.org
Subject: Re: Message Persistence in Qpid Broker C++ (1.39)
On Wed, May 19, 2021 at 5:09 AM Namitha, Nancy <nami...@hpe.com> wrote:
> I have deployed Qpid Broker C++ v 1.39 package on Ubuntu 18.4.
> And have enabled persistence using linearstore libraries. And I am using
> AMQP 1.0 Client Library for GO (https://github.com/Azure/go-amqp) for
> sending and receiving messages.
> When I set the message to be persistent, and send it, it takes min .5
> secs to push the message to the queue, the function to return. If the
> Message is not persistent, it takes less than 1 ms to send the
> message. I am pushing the message to a Persistent Queue
>
> I would like to understand if this behavior is expected if the message is set
> to persistent, or is there any configuration or properties that needs to be
> set to reduce the time taken to push the messages I did not find any proper
> documentation for persistence.
The go client sends messages synchronously, i.e. it waits for an
acknowledgement from the server before returning (you can turn off
acknowledgements using the sender settle mode, but that is probably not what
you want for persistent messages). The broker will not acknowledge the message
until it is sure it is flushed to disk. The
c++ broker is not really optimised for storing a single message at a
time, so the performance for that pattern is indeed likely to be quite slow.
---------------------------------------------------------------------
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
