qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brandon Pedersen <bped...@gmail.com>
Subject Re: DerbyDB vs BerkeleyDB using the Java Broker
Date Sat, 07 Jan 2012 02:50:56 GMT
On Jan 5, 2012 11:45 AM, "Rob Godfrey" <rob.j.godfrey@gmail.com> wrote:
> On 4 January 2012 22:56, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:
> > In terms of BDB vs. Derby performance, I wouldn't be surprised if for a
> > single producer / single consumer case the performance is very similar.
> > Robbie highlights, really the performance here is all to do with how
> > you can synchronously write to disk.  If ach store is performing a
> > write to disk for each transactional commit, then the performance
should be
> > very smilar.
> >
> >
> So, I actually spent a bit of time today testing this out :-)
> The use case that my users most often encounter with persistent messaging
> is where each message sent/received from the broker is sent in its own
> transaction (using JMS), and for the testing I have chosen a 1Kb message
> size.

> The Derby store does indeed provide slightly superior performance if you
> have eight or less active connections, but the BDB store scales better
> above that number. For completeness I have also tested the C++ broker with
> its async store, and another popular AMQP broker implementation
> You can see the results here:
> Note that other test scenarios (in particular not using transactions)
> likely give wildly different comparative performance, and message sizes
> also affect the results.  Obviously people should always test on their own
> hardware and with test cases reflecting their actual usage pattern.
> Cheers,
> Rob

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message