RE: Performances

> From: Eric P.
> 
> Hi again :)
> 
> What performance can we expect with the following configuration :
> 
> 
> 2 servers :
> - Linux
> - Tomcat 5.5.9
> - Embedded OpenJMS server, 0.7.7-alpha-3
> - A router/firewall
> 
> Clients have subscribed to their server with HTTP.
> Servers have (durably-)subscribed to each other with HTTP.
> Publication are called via RPC (we use the embedded 
> connection to publish) Only one topic.
> We send ObjectMessage with a dozen of criteria.
> 
> As I can see,
> Publish a message : 10ms
> Receiving a message : 120ms
> 
> During one test, I sent 47500 non persistent messages, it 
> took 8mn to publish everything and 8mn to receive 1600 
> messages before OutOfMemoryException. I guess OpenJMS server 
> must be overloaded.
> 
> These performance are far from our expectations.
> 
> There are 3 publishing process. We must be able to send 
> simultaneously :
> 1000 messages every 8s (non persistent)
> 10000 messages every 8mn (non persistent) 50 messages every 
> minute (persistent)
>  
> 
> Can we hope a better performance by tuning OpenJMS or not? Do 
> we need to watch other JMS implementations or is it 
> impossible? Do we need to do something different from JMS ?
> 
> Thank you for your help !
> 
> Eric
> 

Some notes:
. http is significantly slower than tcp
. selectors impact performance. They perform a sequential 
  scan of available messages until one matches the specified
  criteria.
. asynchronous delivery is typically faster than synchronous receives.
. 0.7.7 hasn't been performance tuned 

-Tim


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642