[AXIS-1323] Poor performance with large amount of data

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2 Beta
• Environment: Windows XP, Tomcat 5.0.16
• Assignee: Unassigned
• Reporter: Jani Väisänen
• Created: 19/Apr/04 13:07
• Updated: 28/Sep/07 12:53

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()));