DO NOT REPLY [Bug 26252] New: - Axis Performance problem with Wsdd configuration

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26252>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26252

Axis Performance problem with Wsdd configuration 

           Summary: Axis Performance problem with Wsdd configuration
           Product: Axis
           Version: 1.2 Alpha
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: micantunes@bes.pt


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.