Hi list, we were testing jboss for its performance in a messagedriven design. A client was sending 500 messages in a period of 50 seconds to topic 1. Messagedriven bean 1 captured the message, and sent it to topic 2. Messagedriven bean 2 captured the message, and sent it to topic 1. On topic 1, there were 2 subscribers : messagedriven bean 1, and a monitoring client. So messages sent to the system were tripping around in a loop, and the monitoring client could listen to whats going on. Well, here is what the monitoring client told us : after 500 messages, the time a message took between MDB1 and MDB2 was 30 seconds, and jboss was unstable, we never saw the last messages coming back, and waited for somehow 5 minutes to see them. So we decided to stop sending in new messages at only 50 messages. There we could observe that the delay a message took between bean 1 and bean 2 was around 7 seconds. We enlarged the heap size of the VM to go between 128 and 196MB. The results for 50 messages stayed the same. Well, then we decided to increase the number of beans and topics from 2 to 4. So now instead of having messages taking their way between MDB1 and MDB2 continuously, we had 4 beans, and 4 topics between them. We measured the time again, the time a message took while traveling between all 4 beans. Here we got the following results : MDB1 - MDB2 : 16 seconds. MDB2 - MDB3 : 5 seconds. MDB3 - MDB4 : 5 seconds. In all the above cases the CPU usage was VERY low. Hardware : Pentium II 400Mhz, 256 MB RAM, Windows NT4. JVM : Sun JVM 1.3.0rc3, heap size 128-196MB RAM. Message size was one parameter to be tested too - well, here we the following results : when increasing the message size in the above cases, we got MORE CPU usage, and slightly more traveling times for the messages. But hey well, I don't know what to think about it : I envisaged a totally asynchronous and decoupled design for my project : and now I see that at 50 messages circulating in the system, my components can't handle requests at less than 50 requests, I get unacceptable response times ! Am I right here ? What are we doing wrong ? In the design I hoped to realize for my project, every component would be loosely coupled - everything independent, and communicating and cooperating via messages, to handle requests. I would surely have had 100 topics in my system, with around 20 different beans listening for them. But with delivery times of 16 seconds per message, at only 50 messages circulating around (with less than 5 KB each), and only 4 topics, I cant even THINK about implementing this way. Well, damn. Best regards, Jubin Zawar _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
