activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Shared datasource for broker and data?
Date Wed, 28 Feb 2007 10:57:05 GMT
Having one pool or two shouldn't make much of a difference in the
grand scheme of things, assuming the pool has enough connections in
it.

On 2/28/07, drvillo <f.vivoli@gmail.com> wrote:
>
> Hi
>
> I know this might be quite general but I'd like to know someone else's
> opinion.
>
> Given that I use commons dbcp to pool connections, I face two setups:
>
> -activemq uses its own datasource to store transient messages, so I end up
> having two pools
> -activemq shares a datasource with the application logic
>
> The first should be generally more resource consuming but how about
> performance? I don't know which one should perform the best.
> Actually it's difficult to produce a benchmark because the behavior depends
> on
> the access pattern, that is hard to reproduce...
>
> Thanks for your feedback
> Francesco
> --
> View this message in context: http://www.nabble.com/Shared-datasource-for-broker-and-data--tf3308045s2354.html#a9201617
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message