axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1323) Poor performance with large amount of data
Date Mon, 26 Apr 2004 12:19:53 GMT
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Mon, 26 Apr 2004 5:19 AM
Checked in a bunch of changes. please get the latest cvs and the unit test cases in samples/perf
directory. basically run "ant clean" followed by "ant" in ws-axis/java. then run "ant compile
run" in ws-axis/java/samples/perf and report the results to this bug report.

BTW, on a VERY good machine am getting the following:

[junit] Running samples.perf.PerfService_ServiceTestCase
[junit] - >>>> Warming up...
[junit] - Count:1   Time consumed: 265      Return:array length was - 1
[junit] - >>>> Running volume tests...
[junit] - Count:100         Time consumed: 63       Return:array length was - 100
[junit] - Count:1000        Time consumed: 219      Return:array length was - 1000
[junit] - Count:10000       Time consumed: 890      Return:array length was - 10000
[junit] - Count:100000      Time consumed: 7328     Return:array length was - 100000
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.859 sec


View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1323
    Summary: Poor performance with large amount of data
       Type: Bug

     Status: Open
   Priority: Major

    Project: Axis
             1.2 Beta

   Assignee: Davanum Srinivas
   Reporter: Jani Väisänen

    Created: Mon, 19 Apr 2004 6:07 AM
    Updated: Mon, 26 Apr 2004 5:19 AM
Environment: Windows XP, Tomcat 5.0.16

I have compared AXIS and WASP 4.7 with simple test. I'm passing String array to the service
that doesn't do anything to that array. Service only returns a String message. The test measures
the time consumed for the call.

Here are the results:
100		468		717
1000		1418		811
10000		10726		1310
100000		OutOfMem	5176

AXIS can handle small amount of data fairly well, but WASP beats AXIS with larger arrays.

Sample code of the service:

    public String handleStringArray(String s[]){
        String returnString;

        returnString = "array lenght was: " + s.length;
        return returnString;

Sample code of the client:

        String[] s = new String[1000];
        for(int i = 0; i < s.length; i++){
            s[i] = "qwertyuiopåasdfghjklöäzxcvbnm";

        TimeServiceServiceLocator locator = new TimeServiceServiceLocator();
        TimeService service = locator.getTimeServiceAxis();
        start = new Date();
        result = service.handleStringArray(s);
        end = new Date();
        System.out.println("Time consumed: " + (end.getTime() - start.getTime()));

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