Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 86205 invoked from network); 20 Apr 2004 12:01:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Apr 2004 12:01:13 -0000 Received: (qmail 68129 invoked by uid 500); 20 Apr 2004 12:01:07 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 68108 invoked by uid 500); 20 Apr 2004 12:01:07 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 68096 invoked from network); 20 Apr 2004 12:01:07 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 20 Apr 2004 12:01:07 -0000 Received: (qmail 17356 invoked from network); 20 Apr 2004 12:01:53 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 20 Apr 2004 12:01:53 -0000 Message-ID: <308526782.1082462513667.JavaMail.apache@nagoya> Date: Tue, 20 Apr 2004 05:01:53 -0700 (PDT) From: jira@apache.org To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS-1323) Poor performance with large amount of data In-Reply-To: <2121684823.1082380133480.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Davanum Srinivas Created: Tue, 20 Apr 2004 5:01 AM Body: Here are the #'s am getting with latest CVS. Can you try getting the full c= vs instead of getting individual files? clean up your environment and try a= gain? Count:100 Time consumed: 140 Count:1000 Time consumed: 841 Count:10000 Time consumed: 7000 Count:100000 Time consumed: 68479 thanks, dims --------------------------------------------------------------------- View this comment: http://issues.apache.org/jira/browse/AXIS-1323?page=3Dcomments#action_351= 62 --------------------------------------------------------------------- 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=E4is=E4nen Created: Mon, 19 Apr 2004 6:07 AM Updated: Tue, 20 Apr 2004 5:01 AM Environment: Windows XP, Tomcat 5.0.16 Description: I have compared AXIS and WASP 4.7 with simple test. I'm passing String arra= y to the service that doesn't do anything to that array. Service only retur= ns a String message. The test measures the time consumed for the call. Here are the results: ARRAY_SIZE=09AXIS(ms)=09WASP(ms) 100=09=09468=09=09717 1000=09=091418=09=09811 10000=09=0910726=09=091310 100000=09=09OutOfMem=095176 AXIS can handle small amount of data fairly well, but WASP beats AXIS with = larger arrays.=20 Sample code of the service: public String handleStringArray(String s[]){ =20 String returnString; returnString =3D "array lenght was: " + s.length; =20 return returnString; =20 } Sample code of the client: String[] s =3D new String[1000]; for(int i =3D 0; i < s.length; i++){ s[i] =3D "qwertyuiop=E5asdfghjkl=F6=E4zxcvbnm"; =20 } TimeServiceServiceLocator locator =3D new TimeServiceServiceLocator= (); TimeService service =3D locator.getTimeServiceAxis(); =20 start =3D new Date(); result =3D service.handleStringArray(s); end =3D new Date(); =20 System.out.println("Time consumed: " + (end.getTime() - start.getTi= me())); --------------------------------------------------------------------- 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