Hi again,
my experiments have also showed that having Session with
CLIENT_ACKNOWLEDGE mode instead of transacted session and issuing
message.acknowledge() after each consumed persistent message also
gives huge performance grow comparing to Session.commit(). Now I can
consume more than 3000 msg / s
Hi,
resolving TCP_NODELAY issue made Session.commit() fast after each
non-persistent message consumption when broker is running Linux.
However, commit is no longer fast when consuming persistent messages.
Performance running broker both on Windows and Linux is no more than
10 msg / sec.
I suppos
Ah my mistake - that only works on the client side - not on the broker side.
On 9/5/07, James Strachan <[EMAIL PROTECTED]> wrote:
> As described on AMQ_1156, why not use
>
> ?socket.tcpNoDelay=true
>
>
> On 9/5/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I hope tcpNoDelay flag
As described on AMQ_1156, why not use
?socket.tcpNoDelay=true
On 9/5/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I hope tcpNoDelay flag will be updated in next release of ActiveMQ.
> For those using 4.1.1 version there are two workarounds:
>
> 1. Modify the source code as describe
Hi,
I hope tcpNoDelay flag will be updated in next release of ActiveMQ.
For those using 4.1.1 version there are two workarounds:
1. Modify the source code as described in AMQ-1156.
2. In lib/activemq-core-4.1.1.jar edit
META-INF/services/org/apache/activemq/transport/tcp and change
class=org.apa
Hi,
what is the right way to turn off TCP_NODELAY on Apache ActiveMQ 4.1.1
(server side)? Looks like none of the options (socket.tcpNoDelay,
wireFormat.tcpNoDelayEnabled, tcpNoDelay) work as described in
AMQ-1156.
Regards,
Dziugas Baltrunas
On 9/4/07, James Strachan <[EMAIL PROTECTED]> wrote:
>
On 9/4/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> looks like I was wrong - running daemon on Windows increases the
> performance dramatically and I can now consume 1000 messages with
> commit after each message in less then 500 ms. And this is client
> independent, i.e. both c
Hi again,
looks like I was wrong - running daemon on Windows increases the
performance dramatically and I can now consume 1000 messages with
commit after each message in less then 500 ms. And this is client
independent, i.e. both consumer from Linux and Windows can consume
fast from ActiveMQ runni
Hello,
thanks for reply. As I wrote, it does not matter whether I'm consuming
persistent or non-persistent messages. ActiveMQ is running on Linux
local drive with ext3 file system and in all other ways performance is
good, up to several thousand messages per second.
Regards,
Dziugas Baltrunas
On
On 9/3/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> I've noticed that Session.commit() operation is very slow both for
> consumer and producer modes. I'm using Apache ActiveMQ 4.1.1. I tried
> both with persistent and non-persistent messages, switching tcpNoDelay
> and asyncSend/
10 matches
Mail list logo
