Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <19e0530f0407190958ce5eef4@mail.gmail.com>
Date: Mon, 19 Jul 2004 12:58:33 -0400
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: AXIS-1423 : Peter's test case for performance
Cc: dims@apache.org, Tom Jordahl <tomj@macromedia.com>,
	Glen Daniels <gdaniels@sonicsoftware.com>
In-Reply-To: <19e0530f0407190914270c5b8c@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: 
 <80A43FC052CE3949A327527DCD5D6B2758B1D6@MAIL01.bedford.progress.com>
 <19e0530f0407171256665ef942@mail.gmail.com>
 <7E6032F7-D99C-11D8-9ABF-000393DB3A5C@axonstudios.net>
 <19e0530f0407190914270c5b8c@mail.gmail.com>

ok. checked a version with commons' BOAS.

-- dims

On Mon, 19 Jul 2004 12:14:09 -0400, Davanum Srinivas <davanum@gmail.com> wrote:
> Note that i may incorporate Nishant's suggestion of commons'  BOAS and
> ask you to test that as well :)
> 
> -- dims
> 
> On Mon, 19 Jul 2004 08:58:36 -0700, Peter Molettiere
> 
> 
> <pietro@axonstudios.net> wrote:
> >
> > I'll run them this afternoon. Thanks for all your effort! I'll let you
> > know how it goes once I'm at the machine I have my profiler set up on.
> >
> > --Peter
> >
> >
> >
> > On Jul 17, 2004, at 12:56 PM, Davanum Srinivas wrote:
> >
> > > Peter, Nishant, Glen,
> > >
> > > Can you please re-run tests on your machines using latest CVS? i just
> > > fixed http://nagoya.apache.org/jira/browse/AXIS-1202 and that could be
> > > the root cause of the leaks.
> > >
> > > Thanks,
> > > dims
> > >
> > > On Fri, 16 Jul 2004 22:59:35 -0400, Glen Daniels
> > > <gdaniels@sonicsoftware.com> wrote:
> > >> Me too :)
> > >>
> > >> I just got home and had left an OptimizeIt session running before I
> > >> left, so will take a look soon.
> > >>
> > >> --G
> > >>
> > >>
> > >>
> > >>> -----Original Message-----
> > >>> From: Davanum Srinivas [mailto:davanum@gmail.com]
> > >>> 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
> > >>>
> > >>> am still looking :)
> > >>>
> > >>> -- dims
> > >>>
> > >>> On Fri, 16 Jul 2004 18:57:33 -0700, Peter Molettiere
> > >>> <pietro@axonstudios.net> wrote:
> > >>>>
> > >>>> I'll do what I can, although I'm certainly a bit hampered by not
> > >>>> having spent lots of time with the axis source. Someone who really
> > >>>> understands the axis internals would probably be able to find this
> > >>>> much more quickly than I can.
> > >>>>
> > >>>> If you'd like, I'm not far from Macromedia. You're welcome
> > >>> to come by
> > >>>> and take a look at what I'm doing. Maybe two heads can come
> > >>> up with a
> > >>>> solution where one can't.
> > >>>>
> > >>>> --Peter
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Jul 16, 2004, at 11:36 AM, Tom Jordahl wrote:
> > >>>>
> > >>>>>
> > >>>>> Peter,
> > >>>>>
> > >>>>> This is really good work.  It seems like you really have
> > >>> a handle on
> > >>>>> how to reproduce this problem.
> > >>>>>
> > >>>>> Do you have any tools that you could bring to bear on *where* the
> > >>>>> memory leak is in the code?  It sure sounds like you are just a
> > >>>>> 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,
> > >>>>> however, if you set the return message size smaller, you'll still
> > >>>>> see the server side memory leak, it will just take much longer to
> > >>>>> notice, since you have to leak much more memory before the
> > >>>>> serialization/deserialization overhead (which is itself
> > >>> much smaller
> > >>>>> due to the smaller message size) bumps into the max heap
> > >>> size limit.
> > >>>>>
> > >>>>> We're mainly concerned with the server leaking memory,
> > >>> rather than
> > >>>>> the large amount of memory used during
> > >>>>> serialization/deserialization, since it eventually crashes our
> > >>>>> server, whereas we can just install more RAM and increase
> > >>> our heap
> > >>>>> 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.
> > >>> Note that
> > >>>>>> there are 15 threads each issuing 50 calls against a
> > >>> service that
> > >>>>>> delivers a 13 MB XML  (Please edit the client code to
> > >>> restore the
> > >>>>>> original params if needed)
> > >>>>>>
> > >>>>>> http://nagoya.apache.org/jira/browse/AXIS-1423
> > >>>>>>
> > >>>>>> -- dims
> > >>>>>>
> > >>>>>> --
> > >>>>>> Davanum Srinivas - http://webservices.apache.org/~dims/
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Davanum Srinivas - http://webservices.apache.org/~dims/
> > >>>
> > >>>
> > >>
> > >
> > >
> > > --
> > > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> >
> 
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/