Hi Rob,
I had the same issue, and found out that KahaDB performance is heavily
dependent on the maximum sync rate of the filesystem. KahaPersistenceAdapter
is generally faster as described. My questions are:
-is KahaPersistenceAdapter as reliable as KahaDB?
-does it guarantee persistence of que
nice! - thx titexe
On 15 Dec 2009, at 09:21, titexe wrote:
by putting this config KahaDB, I had the same performance as
Kahapersistenceadaptor:
titexe
titexe wrote:
Hello,
using kahaDB, could you have the same performance?
Because I encounter the same problem, even using what i
by putting this config KahaDB, I had the same performance as
Kahapersistenceadaptor:
titexe
titexe wrote:
>
> Hello,
>
> using kahaDB, could you have the same performance?
>
> Because I encounter the same problem, even using what in
> ActiveMQ-througthput.xml
>
> best regards,
>
Hello,
using kahaDB, could you have the same performance?
Because I encounter the same problem, even using what in
ActiveMQ-througthput.xml
best regards,
titexe
Duro wrote:
>
> Hi,
>
> i've tested kahadb and kahaPersistenceAdapter using same simple test
> conditions i.e.
>
> - persistent
Looks like enableJournalDiskSyncs is comparable to the AMQ message store's
syncOnWrite (sync every write to disk) property, which by default it set to
'false'.
http://activemq.apache.org/amq-message-store.html
Joe
Duro wrote:
>
> It seems enableJournalDiskSyncs="false" do the trick, but what
It seems enableJournalDiskSyncs="false" do the trick, but what does this
setting actually do? Is it something i should worry about when disabling
this feature?
Dejan Bosanac wrote:
>
> Hi Duro,
>
> kahadb has some trade-offs for scalability and recovery speed vs.
> performance, but shouldn't t
You should get some improvement on the producer side if you set useAsyncSend
to true.
If you have a relatively small number of destinations and high throughput is
important, the AMQ message store is the way to go.
Joe
http://www.ttmsolutions.com
Duro wrote:
>
> Hi,
>
> i've tested kahadb a
Hi Duro,
kahadb has some trade-offs for scalability and recovery speed vs.
performance, but shouldn't that much slower. You can check
activemq-throughout.xml config and see if applying some the parameters
seen there can help you.
If performance is your main issue (not scalability and recovery) th
