You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/06/06 07:56:57 UTC
[jira] Assigned: (AXIS-1199) Axis Performance problem with Wsdd configuration
Message:
The following issue has been re-assigned.
Assignee: Davanum Srinivas (mailto:dims@yahoo.com)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1199
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1199
Summary: Axis Performance problem with Wsdd configuration
Type: Bug
Status: Open
Project: Axis
Components:
Deployment / Registries
Versions:
1.2 Alpha
Assignee: Davanum Srinivas
Reporter: Miguel Antunes
Created: Mon, 19 Jan 2004 4:07 PM
Updated: Sat, 5 Jun 2004 10:56 PM
Environment: Operating System: All
Platform: All
Description:
Hi,
I have experienced a poor performance on Axis when using wsdd configuration
with a large amount of services. I have deployed about 800 services in axis,
each service with 3 methods, and two type mappings. The first time I invoke a
service or ask for its Wsdl the response time is about one minute (the service
execution time is about 300 ms). I have profiled Axis and found that most of
the time was spent in the org.apache.axis.deployment.wsdd.WSDDService
constructor, more precisely in its last two statements:
" ...
// Initialize TypeMappingRegistry
initTMR();
// call to validate standard descriptors for this service
validateDescriptors();
.."
After looking at the class more carefully I noticed that axis is prepared for
on demand initialization so I just commented out those two lines, the results
were very satisfactory. The following table gives a little resume:
-------------------------------------
Before optimization After optimization
List all service +- 120 sec 60 sec
First service wsdl >60 sec <10 sec
query after boot
First service call >60 sec <10 sec
after boot
-------------------------------------------
Note: Since these numbers were obtained in my development environment, their
absolute values are not relevant. What is relevant is the difference between
the numbers for the two axis versions.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira