[rabbitmq-discuss] [Minimum Air Induction] Introducing Shovel: An AMQP Relay

Valentino Volonghi dialtone at gmail.com
Sat Sep 20 21:41:29 BST 2008

Hash: SHA1

On Sep 20, 2008, at 12:45 PM, Matthias Radestock wrote:

> Valentino Volonghi wrote:
>> Well, a transaction each 100-500 messages is basically as fast as  
>> no  transaction at
>> all with the difference that the connection is used in bursts  
>> rather  than continuously.
> Why would the connection be used in bursts?

This is what I saw on a test. I suppose that's because until the  
transaction is
committed shovel doesn't see messages coming and if the time between 2  
is long enough to transmit the messages to the remote server then  
there we go and
the bandwidth usage drops until the next commit is done. In this case  
though you are
probably right and the internet wouldn't be fast enough so the usage  
shouldn't burst.

>> 2. shovel reads up to 500 messages and starts a transaction with  
>> the  remote
>>     node sending all of them and committing the transaction.
> Why would you read 500 messages and *then* start a transaction? Just  
> start the tx first, pass the messages through, and send a tx.commit  
> every ~500.

Yes, the 'and' is a logic AND in that sentence, both those things are  
done at the
same time, while the transaction is open shovel reads and forwards.

- --
Valentino Volonghi aka Dialtone
Now running MacOS X 10.5
Home Page: http://www.twisted.it

Version: GnuPG v1.4.9 (Darwin)


More information about the rabbitmq-discuss mailing list