-
1. Re: Pubish/Subscribe Speed, Latency and Limits
adrian.brock Apr 25, 2003 12:47 PM (in response to schoeto)The subscribe is always slower than
the publish.
First, it does twice as much work as the publish
(it does a receive and an acknowledge request)
Second, you push the message to 450 clients
concurrently whereas the publish was just one
client.
Sadly, there is no flow control, but as 3.0.7/3.2,
the message cache should act as a brake on the
publisher.
If memory becomes tight, the publishing thread
is used to push messages out to disk to make room
for the new message. A sort of One-in-One-out
policy.
The OutOfMemoryException is caused by the
message cache settings - use search to find an
explanation.
I have never measured the relative performance
of the serialization. If you do decide to measure
it, maybe you can post the results?
NOTE: Some of the implementations contain
workarounds for bugs in jdk1.3 which makes
them slower than they could be.
Regards,
Adrian -
2. Re: Pubish/Subscribe Speed, Latency and Limits
schoeto Apr 29, 2003 10:38 AM (in response to schoeto)I did several test case comparisons between a MapMessage and a StreamMessage for message delivery speed. I was able to double the speed. My test case involved publishing 1000 messages to one subscriber. The message was small and contained 3 double values.