axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1497) AXIS2: performance improvements
Date Tue, 21 Sep 2004 20:36:39 GMT
The following comment has been added to this issue:

     Author: Aleksander Slominski
    Created: Tue, 21 Sep 2004 1:35 PM

you can find Java test driver here:

and all AXIS C++ service code i have written here:

let me know if you have problems with this - first make sure that test driver self-tests work
then you may need to port AXIS C++ service code to accomodated for AXIS C++ chnages since
May 2004

View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1497
    Summary: AXIS2: performance improvements
       Type: Test

     Status: Unassigned
   Priority: Major

    Project: Axis
             Basic Architecture

   Reporter: Aleksander Slominski

    Created: Fri, 6 Aug 2004 10:29 AM
    Updated: Tue, 21 Sep 2004 1:35 PM
Environment: ALL

this is umbrella issue to record discussion and links to other issues related to performance,
memory footprint, and general architecture

at minimum i think it is important to profile current AXIS 1.x and identify places where performance
problems occur.

to facilitate this a set of tests/benchmarks should be used, currently i know about following

* SOAP Benchmark Suite for Scientific Computing 
-- source code available; that benchmark emphasizes support for very small and very large
messages (sending binary data and large arrays):

(i am main author of this benchmark so i can help with running it, interpreting results and
identifying problems/solutions)

* Dennis Sosnoski's Clean SOAP benchmark 
-- source code available; that benchmark seems to emphasizes doc/literal:

Additional links:

* "Performance and Load-Testing of Axis with Various Web Services Styles" by Rajal Shah, Naresh
Apte (Date: July 16, 2004)
--  no links to code used for testing?

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message