Hi Didier,
We're in the process of building an application that would make heavy use of self-describing messaging. I've been tasked with finding people who are using Sun's JMQ in production and soliciting feedback. I just read your reply and I have some follow-on questions about your experiences:
1.Can you estimate your average and peak message rates in this system?
2.What is the mean message size?
3.What's your level of satisfaction with the GlassFish/JMQ combination?
If you happen to see this reply and have a few minutes, I'd love to hear whatever feedback you can offer.
Thanks in advance,
Scott
hello,
I am just doing a simple test , on a single laptop (win xp, 2 gigaHz, 2 gigBytes), with two mq 3.6EE brokers in cluster, using the mq4 universal client to send a 512 bytes messages every 4 ms, consuming every 3 ms, sending 50K messages;
here are first stat figures provided by master broker:
[30/avr./2007:22:34:43 CEST]
Connections: 1JVM Heap: 265486336 bytes (257005696 free) Threads: 2 (32-2010)
In: 12052 msgs (9570234 bytes) 25712 pkts (11168696 bytes)
Out: 11288 msgs (9685222 bytes) 22600 pkts (10786686 bytes)
Rate In: 162 msgs/sec (128940 bytes/sec) 368 pkts/sec (153016 bytes/sec)
Rate Out: 170 msgs/sec (145924 bytes/sec) 340 pkts/sec (162482 bytes/sec)
this appears to consume cpu on producer/consumer process;
not so bad on a mono cpu box ... ;)
Bonsoir,
Didier