[
https://jira.jboss.org/jira/browse/JBESB-2802?page=com.atlassian.jira.plu...
]
Martin Vecera commented on JBESB-2802:
--------------------------------------
We tried bypassing different parts of HttpRouter and seems that the problem is in
executing HTTP method. But the code in SOAPClient seems to be the same. Why is there such
a big difference? And one more thing - if we used getResponseBodyAsString() in HttpRouter,
we saw that well known warning "Going to buffer a response of unknown size". On
the other hand, SOAPClient uses the same method but the warning is not displayed.
HTTPRouter is 4 times slower than SOAPClient under heavy load
-------------------------------------------------------------
Key: JBESB-2802
URL:
https://jira.jboss.org/jira/browse/JBESB-2802
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP3
Environment: SOA-P 4.3.CP02 CR2, 3x server with 8 CPU cores, tried both Sun JVM
1.6 x86_64 and OpenJDK 1.6 x86_64, RHEL5
Reporter: Martin Vecera
Priority: Critical
I have a configureation of 3 servers:
1) a client generating HTTP requests in 100 threads (i.e. simulating 100 clients)
2) SOA-P with a EBWS service that forwards requests to 3rd server using either HTTPRouter
or SOAPClient
3) a plain helloworld Web Service
When there is just one client, HTTPRouter is definitely faster than SOAPClient. But under
the heavy load (100 clients, 500 000 messages, 5kB each), HTTPRouter can process 2.5
messages per thread and SOAPClient can process 10 messages per thread.
HTTPRouter - Average 19002264ms, messages 44920 (2.363928845531248 msgs/sec)
SOAPClient - Average 17586237ms, messages 187705 (10.673403298272392 msgs/sec)
I'm futher investigating the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira