> Turning off the compression makes a small difference (about 1/2 a
> message /
> second). Is there any supporting configuration required on the
> routers?
I tested it here yesterday only for the publisher side. Testing the
subscriber side I realized that the throughput is highly dependend on how
many values I set in the MapMessage. When I set up to 5 values
(String/Integer mixed), it is ok (more or less). When I set a 6th value,
it slows down on the subscriber side to ~ 4 msgs / sec.
For MapMessage and StreamMessage the Java object serialization is used (in
contrast to the other msg types where an own optimized serialization is
used). We will change this ASAP and will provide a patch via
www.swiftmq.com, maybe this weekend.
Sorry for any inconviences!
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ, JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
