Hi Tim,
I have seen the same problem. I have been concentrating on the Client side and have done almost all I can so far there. I would recommend setting up a SOAP pool. The pool design pattern will help a lot with the client side. I would create the service object once then create a pool of call objects.
On the server side I would use worker thread pattern. I have not tried this myself yet but have hopes it will help me cut down the transaction times since there is not a big concurrency issue for my app.
Also, depending upon your application and the data you might want to consider local/regional cache architecture.
I did ask the question in this group if the Axis servlet is single threaded but have not gotten an answer. If it is then there will always be performance issues if the transaction times are slow downstream of the axis servlet and due to the nature of request/response and http being blocking so the next http request into the single servlet has to wait till the last request is finished.
Hope this helps,
Tony
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 05, 2003 9:47 AM
To: [EMAIL PROTECTED]
Subject: Performance
I'm seeing dreadful performance using Axis with multiple concurrent calls.
I have a simple test app which runs some PL/SQL. In single user mode, it works quickly across an Axis call (Axis on both client and server), taking about a second to complete.
I've ramped up the app and have 10 concurrent threads doing the same call. The PL/SQL is now taking between 140ms and 1372ms, which is fair enough, and the actual call after the Axis bit (ie inside the method that is exposed using Axis) varies between 2173ms and 2424ms.
These figures I can live with, and I'm sure there are further optimizations I can put into my architecture to reduce this time.
However, the total call time varies between 7331ms and 10445ms. I appear to be losing between 5 and 8 seconds simply doing Axis comms.
Anyone got any tips on how to speed this up, or ideas of why it's so bad?
Axis 1.1rc1, JBoss 3.0.4 app server, jdk 1.4.0, windows NT.
Tim.
