Auto ack it did 8k msgs/sec. Using transactions, and one msg/transaction it did 5.5k.
This was p2p, 1:1 run 16 times in parallel, to give the best possible opportunity for parallelism and tricks like write combining. I was impressed. On 08/11/2007, Robert Greig <[EMAIL PROTECTED]> wrote: > > On 08/11/2007, Rupert Smith <[EMAIL PROTECTED]> wrote: > > > By batching, I mean that on a disk that can only do maybe 500 IOPS, by > > combining (batching) writes, it manages 8k msgs/sec. We can get similar > > results for Qpid when running under transactions, and sending 10 > > msgs/transaction, but in auto ack mode our write combining strategy does > not > > seem to be quite so effective, giving a result closer to the 500 for > that > > particular test. I'm not sure exactly why that is. Perhaps its all down > to > > our choice of transaction logger. Perhaps our write combining strategy > is > > not active in auto ack mode. > > So you're saying that Swift can do 8k msgs/sec with a single commit per > message? > > RG >
