2008/5/20 Senaka Fernando <[EMAIL PROTECTED]>:

> Thanks for the valuable guidelines. I'm almost done writing the README for
> the config.xml.

Great work!

> However, I'm yet to understand the,
>
>    <advanced>
>        <filterchain enableExecutorPool="true"/>
>        <enablePooledAllocator>false</enablePooledAllocator>
>        <enableDirectBuffers>false</enableDirectBuffers>
>        <framesize>65535</framesize>
>        <compressBufferOnQueue>false</compressBufferOnQueue>
>        <enableJMSXUserID>false</enableJMSXUserID>
>    </advanced>
>
> section. As it seems it is a bit advanced to figure out. :)...

OK, from the top - many of these are actually MINA specific - if
anyone spots that I am talking nonsense please jump in and correct me:

enableExecutorPool specifies whether to add a threadpool filter to the
filterchain - basically means that the I/O is done in a separate
thread from the processing. This really should never be set to false.

pooled allocator means that MINA will pool byte buffers. Testing has
shown that this counterproductive when using heap buffers (see next
point)

direct buffers are the NIO direct byte buffers - as opposed to heap
buffers. In theory they are supposed to be faster but on the operating
systems and JVMs that we have tested (RHEL 3 and 4, sun and BEA) we
find that heap buffers are better. YMMV.

framesize - the maximum framesize the broker will use for AMQP frames.
Messages bigger than this size will be fragmented into frames of this
size. It may be worth increasing the size to increase throughput if
you send messages a little bit bigger than this but obviously this
needs careful testing etc etc

compressBufferOnQueue - by default, for performance, byte buffers
representing data read off the network are not compressed. This is
sensible if the data is just about to go straight out to a client.
However it does mean that the memory usage will be high (see the
comments earlier about the socket buffer sizes) so setting this to
true should reduce memory usage particularly if you have slow clients.

JMSXUserId - no idea I'm afraid.

> Also, there are two elements configuring virtualhosts. I would like to know
> how this works out.

Anything specific?

Not sure myself about the virtualhosts directory - is it perhaps where
to look for the virtualhosts xml files?

RG

Reply via email to