Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AXIS-1423 : Peter's test case for performance
Date: Fri, 16 Jul 2004 22:59:35 -0400
Message-ID: 
 <80A43FC052CE3949A327527DCD5D6B2758B1D6@MAIL01.bedford.progress.com>
Thread-Topic: AXIS-1423 : Peter's test case for performance
Thread-Index: AcRrqdHvnwzAS8aWR9K3QH7PSZHYvAAADFIg
From: "Glen Daniels" <gdaniels@sonicsoftware.com>
To: <dims@apache.org>, "Peter Molettiere" <pietro@axonstudios.net>
Cc: "Tom Jordahl" <tomj@macromedia.com>, <axis-dev@ws.apache.org>

Me too :)

I just got home and had left an OptimizeIt session running before I
left, so will take a look soon.

--G=20

> -----Original Message-----
> From: Davanum Srinivas [mailto:davanum@gmail.com]=20
> Sent: Friday, July 16, 2004 10:58 PM
> To: Peter Molettiere
> Cc: Tom Jordahl; dims@apache.org; axis-dev@ws.apache.org; Glen Daniels
> Subject: Re: AXIS-1423 : Peter's test case for performance
>=20
> am still looking :)
>=20
> -- dims
>=20
> On Fri, 16 Jul 2004 18:57:33 -0700, Peter Molettiere=20
> <pietro@axonstudios.net> wrote:
> >=20
> > I'll do what I can, although I'm certainly a bit hampered by not=20
> > having spent lots of time with the axis source. Someone who really=20
> > understands the axis internals would probably be able to find this=20
> > much more quickly than I can.
> >=20
> > If you'd like, I'm not far from Macromedia. You're welcome=20
> to come by=20
> > and take a look at what I'm doing. Maybe two heads can come=20
> up with a=20
> > solution where one can't.
> >=20
> > --Peter
> >=20
> >=20
> >=20
> > On Jul 16, 2004, at 11:36 AM, Tom Jordahl wrote:
> >=20
> > >
> > > Peter,
> > >
> > > This is really good work.  It seems like you really have=20
> a handle on=20
> > > how to reproduce this problem.
> > >
> > > Do you have any tools that you could bring to bear on *where* the=20
> > > memory leak is in the code?  It sure sounds like you are just a=20
> > > single step away from finding the leak.
> > >
> > > --
> > > Tom Jordahl
> > > Macromedia Server Development
> > >
> > > -----Original Message-----
> > > From: Peter Molettiere [mailto:pietro@axonstudios.net]
> > > Sent: Friday, July 16, 2004 2:27 PM
> > > To: dims@apache.org
> > > Cc: axis-dev@ws.apache.org; Glen Daniels
> > > Subject: Re: AXIS-1423 : Peter's test case for performance
> > >
> > >
> > > Hey guys,
> > >
> > > We set the numbers high to make the problem manifest easily,=20
> > > however, if you set the return message size smaller, you'll still=20
> > > see the server side memory leak, it will just take much longer to=20
> > > notice, since you have to leak much more memory before the=20
> > > serialization/deserialization overhead (which is itself=20
> much smaller=20
> > > due to the smaller message size) bumps into the max heap=20
> size limit.
> > >
> > > We're mainly concerned with the server leaking memory,=20
> rather than=20
> > > the large amount of memory used during=20
> > > serialization/deserialization, since it eventually crashes our=20
> > > server, whereas we can just install more RAM and increase=20
> our heap=20
> > > size to get around the gobs of memory used during serialization.
> > >
> > > --Peter
> > >
> > > On Jul 16, 2004, at 9:26 AM, Davanum Srinivas wrote:
> > >
> > >> Glen,
> > >>
> > >> Uploaded a slightly revved version of Peter's test case.=20
> Note that=20
> > >> there are 15 threads each issuing 50 calls against a=20
> service that=20
> > >> delivers a 13 MB XML  (Please edit the client code to=20
> restore the=20
> > >> original params if needed)
> > >>
> > >> http://nagoya.apache.org/jira/browse/AXIS-1423
> > >>
> > >> -- dims
> > >>
> > >> --
> > >> Davanum Srinivas - http://webservices.apache.org/~dims/
> >=20
> >=20
>=20
>=20
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>=20
>=20