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 Wed, 21 Apr 2004 18:20:59 GMT
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Wed, 21 Apr 2004 11:20 AM
Here's the result running against latest CVS (see the sample code that i uploaded as well).

>>>> Warming up...
Count:1         Time consumed: 2253     Return:array length was: 1
>>>> Running volume tests...
Count:100       Time consumed: 131      Return:array length was: 100
Count:1000      Time consumed: 440      Return:array length was: 1000
Count:10000     Time consumed: 1803     Return:array length was: 10000
Count:100000    Time consumed: 9423     Return:array length was: 100000

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: Wed, 21 Apr 2004 11:20 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