axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1323) Poor performance with large amount of data
Date Tue, 27 Apr 2004 06:03:53 GMT
The following comment has been added to this issue:

     Author: Jani Väisänen
    Created: Mon, 26 Apr 2004 11:03 PM
       Body:
Here are my results:

[junit] Running samples.perf.PerfService_ServiceTestCase
[junit] - >>>> Warming up...
[junit] - Count:1   Time consumed: 484      Return:array length was - 1
[junit] - >>>> Running volume tests...
[junit] - Count:100         Time consumed: 93       Return:array length was - 100
[junit] - Count:1000        Time consumed: 422      Return:array length was - 1000
[junit] - Count:10000       Time consumed: 1232     Return:array length was - 10000
[junit] - Count:100000      Time consumed: 8984     Return:array length was - 100000
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 12,4 sec

Pentium 4 2.4GHz, 1GB of RAM, WinXP

The results are great - thank you! Great work!
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1323?page=comments#action_35291

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1323

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
   Versions:
             1.2 Beta

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

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

Description:
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:
ARRAY_SIZE	AXIS(ms)	WASP(ms)
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()));


---------------------------------------------------------------------
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


Mime
View raw message