Andreas,
we're using 1.2a, download date: 2000/11/16.
The ordinary message length is <300 bytes, persistent messages only.
We're running the clients on NT workstation 4.0, SP5.
We also tested with one router only on the sender site, This showed no
significant performance improvement.
Edwin
-----Ursprüngliche Nachricht-----
Von: Andreas Mueller [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 7. Dezember 2000 11:17
An: [EMAIL PROTECTED]
Betreff: [developers] SwiftMQ performance
> We tested several configurations which all showed the same trend:
> SwiftMQ is of high performance on the sender side (up to 190 msg/sec.)
> but
> quite slow on the receiver side (average of 5 - 40 msg/sec. depending
> on the
> configuration).
>
> Thus, we think we're doing something wrong in our configuration and
> there
> should be a way to speed up the receiver.
Are you using 1.2b? Are your clients NT Workstation? There is a known
problem with NT WS. With uncompressed bigger msgs there is a rate of only
5/secs with CPU utilization of nearly 0. You should use 1.2b with
compression on (the default). Actually a receiver should be able (when
connected to a router on the same machine) to receive > 1000 msgs/sec,
size 1k, non-persistent, all msgs in cache, no concurrent sender.
Throughput for persistent msgs should be > 300.
> It was striking in the 2-router-configuration with static routes and
> remote
> queues that the message transfer from the "sender router" to the
> "receiver router" was extremely slow (about 5 msgs/sec.).
That seems the same problem as above.
> Is it normal behaviour in this configuration that the persistent
> messages
> are stored locally at the "sender router" before they're being
> transferred
> to the receiver?
Yes. Messages are committed locally for the sender and are stored in a
destination (remote router) outbound queue and are forwarded from there to
the destination router, maybe via different hops, may be round robin over
different routes. The destination router stores them in the destination
queue. For persistent msgs, every router must write the msg to disk. There
is no other way because of the guaranteed delivery. If you want to speed
up the delivery time sender->receiver, you must reduce the hops between
them, thus, use just one router where all are connected to.
--
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/
------------------------------------------------------
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/
