It's also possible that 8 isn't the optimal pool size for your test driver,
and that a different (presumably larger) value would give better
throughput. Tuning the pool size of any pooling technology (ActiveMQ,
JDBC, etc.) is an iterative and experimental process, and your first guess
often won't
I agree with Robbie's comments here. The statement that the application only
creates the connections once got me confused at first, but looking at the
original post, the pseudo-code there clearly creates the connection once on
each producer.
To verify, start up the application and use one of the
Ok, so it looks like points from the earlier replies of both Tim and
myself would seem to apply then.
You arent creating and closing lots of connections repeatedly over
time, which is about the only situation a pool will help improve
performance in.
The non-pooled factory doesnt give you back the
On Tue, Feb 23, 2016 at 12:25 PM, Robbie Gemmell
wrote:
> I can't say for sure from your summarised description and partial
> code, but it seems like you may only ever create 1 connection object
> with the factory. If so, explicitly creating multiple connections and
> splitting your producers acr
On 23 February 2016 at 10:53, Frizz wrote:
> On Mon, Feb 22, 2016 at 5:32 PM, Timothy Bish wrote:
>
>> ... and for the case of many senders you might
>> indeed see a performance drop since you are now reducing the number of
>> connections to what looks like eight, so all those producers are now
>
On Mon, Feb 22, 2016 at 5:32 PM, Timothy Bish wrote:
> ... and for the case of many senders you might
> indeed see a performance drop since you are now reducing the number of
> connections to what looks like eight, so all those producers are now
> restricted to eight connection to shovel all thei
Without seeing the full code it is hard to comment on the impact the
pool would have in your specific use case. If your threads aren't
trying to create a connection each time then you wouldn't see a
performance improvement, and for the case of many senders you might
indeed see a performance drop s
Hi there,
I am experimenting with a Pooled Connection Factory - but I don't see any
performance gain (even worse: using PooledConnectionFactory is slower than
ActiveMQConnectionFactory).
What I do: Sending a few 100.000 messages in several threads (using
CompletableFuture). Ond run with a ActiveM
