axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: AXIS-1423 : Peter's test case for performance
Date Sat, 17 Jul 2004 02:57:31 GMT
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/

Mime
View raw message