On 08/08/17 02:05, Pankaj Bhagra wrote:
I am trying to extract bulk messages from azure SB.

As per their documentation the azure SDK doesn't support bulk read message
and recommends using the native amqp for the Azure Service Bus. White
trying to negotiate a session with the azure SB, i noticed that independent
of what client is requesting, the SB dials down the incoming_window=5000.
This limits a max of 5000B send per bulk read, thus my consumer runs dry
till the RTT (which is large for inter cloud) to fetch a new packet.

Is this a restriction of the azure SB or am i not setting any/some of the
parameters correctly from the client side to achieve the negotiated window
size  > 5000B.

I am using python proton MessagingHandler Class and clearly see that
on_message is called for few pkts composing of buffer size ~5000B and then
have to wait for the RTT delay to get the next batch.

Any suggestion to work around this problem and get larger bulked message ?
I can't reduce the RTT between the server and consumer. have some
workaround for parallel consumers but would like to solve the bulk problem
as that is most efficient way of achieving the high throughput.

The incoming window is set by each peer independently (i.e. it is not negotiated) and only covers the incoming transfers. For a link receiving from service bus, the incoming window set by service bus isn't relevant. It is the clients incoming window that would affect transfers from service-bus to client.

How large are the messages? From the protocol trace it looks like you are issuing 100 link credits. If the messages were all 50 bytes, that might explain the limited batches you are seeing? You could try increasing that link credit window.

To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to